cmd/go: diagnose collisions between standard-library packages and packages provided by modules #39285
Comments
If the replacement path is The thing we should diagnose is a module (either the main module or one slotted in by a |
By diagnose, what exactly do you expect @bcmills , a log that warns of collisions at the same import path? |
By “diagnose” I mean ”emit an error for the affected packages if they are ever loaded”. I wouldn't recommend that anyone work on this issue right now, because I'm in the middle of refactoring the module-mode loader for #36460 and the merge conflicts would probably be pretty unpleasant. |
This also isn't specific to |
As discussed on golang-dev@, this currently runs without warnings/errors, but doesn't do what I'd intuitively expect:
/cc @bcmills
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.
The text was updated successfully, but these errors were encountered: