Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
cmd/go: ambiguous import path not detected when the colliding path is in the standard library #35270
Suggest in Go 1.14 we go one step further when
When trying to create a module
Perfect, but if you do that inside gopath
Not only is it allowed, you even launch the wrong test files from
I understand this is done for backward compatible sake, but GOPATH must die and end up somewhere as a dot folder hidden only used for cach.
Furthermore I suggest to change error message
to stop promoting people to use GOPATH
(related to: #35070)
This has ~nothing to do with specifying module paths: it would be conceptually ok (if somewhat fragile) to create a
The problem here is that the existing