cmd/go: allow 'go mod tidy' to proceed despite errors #26603
When adding module definitions to existing repositories, we may (often?) find that one or more existing packages do not actually build, or that some import cannot be resolved due to a bug (e.g., #26602).
Failure to build is especially likely for files with rarely-used build constraints, but rarely-used constraints are exactly the space that
If the user needs to intervene to fix something, it would be nice if they could generate the rest of the module definition before they start trying to troubleshoot one or two packages that still won't build. For example, here is the output of