@samthanawalla requested issue #66092 to be considered for backport to the next 1.21 minor release.
@gopherbot pretty please backport this to 1.21 and 1.22
Comment From: gabyhelp
Similar Issues
- cmd/go: always pass -lang to cmd/compile [1.22 backport] #68049
- cmd/compile: Go 1.22 changes support for modules that declare `go 1.0` [1.22 backport] #65619
- cmd/compile: internal compiler error: missed typecheck [1.21 backport] #61909
- cmd/go: build fails when setting linker to lld using ldflags [1.11 backport] #27293
- cmd/go: mod tidy reports toolchain not available with 'go 1.21' [1.21 backport] #67235
- cmd/go: mod tidy reports toolchain not available with 'go 1.21' [1.22 backport] #67236
- cmd/go: accept -Wl,-R,path [1.12 backport] #32168
- cmd/go: TestScript/gotoolchain_issue66175 fails on tip locally [1.21 backport] #67310
- cmd/compile: "only supported as of -lang=go1.13" error is misleading [1.13 backport] #33761
- cmd/go: TestScript/gotoolchain_path fails if golang.org/dl/go1.21.1 is installed in the user's $PATH [1.21 backport] #62711
(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)
Comment From: gopherbot
Change https://go.dev/cl/593295 mentions this issue: cmd/go: set GoVersion for files on the command line with vet
Comment From: samthanawalla
Not backporting this change. A workaround exists.