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
cmd/go: diagnose collisions between standard-library packages and packages provided by modules #39285
As discussed on golang-dev@, this currently runs without warnings/errors, but doesn't do what I'd intuitively expect:
Edit: For posterity, my "intuitively expected" behavior here is/was that the import of "go/types" should be remapped to "./nonexist", and cause a build error because it doesn't exist.
If the replacement path is
The thing we should diagnose is a