/ go Public
cmd/go: workspace recursive add should skip malformed module definitions #51959
Feedback is required from experts, contributors, and/or the community before a change can be made.
What version of Go are you using (
Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (
What did you do?
What did you expect to see?
Expected to see a functional workspace to be created, which should have no effect over the final
go run hello.gocommand.
What did you see instead?
An un-usable workspace was created due to the
toolsrepo containing some purposefully invalid
go.modfiles meant for unit testing, which
go work use -r .added to the workspace, causing the final
go run hello.gocommand to fail with:
go work use -rshould probably print a warning message for each malformed module definition that it encounters instead of adding those to the workspace.
The text was updated successfully, but these errors were encountered: