Description
As reported in golang/go#50085 go 1.18 changes the encoding of the build info.
That means, if a tool is compiled with go1.18 and VS Code is configured to work with different versions of Go, go version -m
command will fail.
The extension currently relies on go version -m
for two things
-
Diagnosis tool that retrieves tools versions
This will affect only diagnosis. In this case we need to request users to reinstall all tools. -
Tools update & consistency check logic:
vscode-go/src/goInstallTools.ts
Line 673 in ed978a6
This will stop tools update notification and compatibility check.
We thought about utilizing go version -m
to improve our tool update logic, but now I am afraid that this is an evidence that we shouldn't rely on go version -m
unless the go version is the latest.
Currently the extension does not have logic to install the latest go version, or allow users to use different toolchains for tool management (probably we should. #825).