cmd/go: mod why -m is not strict when parsing an import path #36658
Labels
Milestone
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
In a project that depends on
golang.org/x/tools/go/packages
, I executedWhat did you expect to see?
as it is done by
go mod init
.What did you see instead?
The text was updated successfully, but these errors were encountered: