Is there some functionality to list each build constraint that is not satisfied when the result of go get is "build constraints exclude all Go files in ..."?
go mod why is very helpful when module dependencies are to be explained. A similar functionality would be helpful and maybe a message to refer to this functionality when "build constraints exclude all Go files in ..." is the conclusion. (For a random package I've found on pkg.go.dev it took a few confusing minutes until I realized that cgo requirement is the build constraint.) On a tangential note: would anybody else be interested to help with issue https://github.com/golang/go/issues/39195 ? (Probably all build constraints should be searchable.) -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CA%2Bctqrq1%2BSVDQO3ecgyj7Kq4Qv6-tE3QWFTrVHtNqro8hUCwCw%40mail.gmail.com.
