Michael Matloob

I don't think it's right to remind the user to check if GOSUMDB is off before suggesting `go work use`. It's cluttered and most users most of the time won't...

@raghvenders I think the error messages suggested by @lpar are reasonable because they help they user who set GOSUMDB=off get a better idea of what's going on so that they...

I don't know if it's worth making the change in https://go.dev/cl/585955 if it's only going to be used by users who enable a custom script locally.

cc @samthanawalla This seems like it could be useful.

I would expect `go install package@version` to use the toolchain in the `go.mod` file of the module version being installed. In this case it looks like the latest released version...

Hm I think I still need to understand something. Now that 1.21 and 1.22 are the last two versions of Go, can we assume that everyone (that we support) has...

Hi, after discussing with @hyangah and with @rsc and @samthanawalla, we've decided to change the toolchain switching behavior for go install package@version and go run package@version: Currently it essentially runs...

Okay, so reading "use directives will be added for directories that exist, and removed for directories that do not exist", the subject for both "added" and "removed" seems to me...

Oh I see. The behavior is that only directories that would be under the tree specified with `-r` _and_ which do not exist would be removed. I'm not sure how...

@MikeMitchellWebDev at which commit were you running make.bash? I understand the build doesn't fail reliably, but are you still able to reproduce occasionally?