/ go Public
cmd/go: "conflicts with" message is too vague when one path is a package and the other is a module #46426
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
From a Slack conversation with @myitcv and @jayconrod:
That error message is decidedly suboptimal: it's saying that the constraint
gopher.live/ub8a7a486d202/mod@none(which is interpreted as a module path) conflicts with
gopher.live/ub8a7a486d202/mod/v2@latest(which is a package query resolving to the same module at
The text was updated successfully, but these errors were encountered: