/ go Public
cmd/go: do not lookup "parent" modules automatically to resolve imports #33568
A change that should be done early in the 3 month dev cycle.
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
One of the most annoying missteps the go command makes is when you mistype an import path in your own module and it goes looking for parent modules that might provide the import. In general that's fine, but I think automatic download and search of parents of the main module should be disabled - it's almost always a typo, and if not the user can run go get explicitly.
For example if I am in module rsc.io/tmp/x and import rsc.io/tmp/x/foo instead of rsc.io/tmp/x/boo, it should not try to download rsc.io/tmp and rsc.io to find rsc.io/tmp/x/foo.
/cc @bcmills @jayconrod
The text was updated successfully, but these errors were encountered: