tree add68f7902e783c8bf6b9d0cf5c5301a7a0bab27
parent bc1a24c218ac7120833eaa81b18f7273025346e6
author Hyang-Ah Hana Kim <hyangah@gmail.com> 1587001526 -0400
committer GitHub <noreply@github.com> 1587001526 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJel7i2CRBK7hj4Ov3rIwAAdHIIAJtbbM3DD6jbnnlP+Mjed/h1
 6dmXhzlzncVSlKFEcWHU2CXXPay4LvvBzL68huPRZNGBC2r1dWz3/LlRBOCUTDjn
 V49ywLFNh+jWP6aFnP1DIU51gL16M9Z2PadZX/6J4WVkxrrgSiqjxvCiZLnNR0Rw
 q7npkN4+3NdmFYG17YEY+4QF5juFx9pxpPPjbs0AvayIoBZFWa0s6s6nSyoXutiU
 0Gdt7tRHcQLMX/sv3TAtakCQ+FKUNxFXaiKu1jSuxYooFzeFf1E88fhTtkuyql/G
 tnk4qDgBRV5unh/8AoU0/3fG0n87GIy/y4EyXca9nL9CYzJc+RthoXvO7lM38HA=
 =lYj0
 -----END PGP SIGNATURE-----
 

Place the go runtime base path to the front of PATH (#3159)

Users can specify the go command to use by setting GOROOT env var,
`go.goroot` vscode setting, or PATH env var. getBinPath('go') is
used to choose the right version of 'go' whenever the extension
tries to invoke the go commands. However, this does not affect
other tools that invoke the go command underneath.

For example, delve, gopls, and many tools simply pick a version of
go from PATH. If the GOROOT env var and the version of go found in
the PATH don't match, this can lead to errors.

This CL places the go runtime base bin path as the first element of
the PATH env var. That ensures any tools invoked by the extension
to pick the same version of go, as long as they stick with the usual
PATH-based executable search.

Note this process.env mutation does not affect the environment variable
settings the integrated terminal would see, but this is not a new
problem.

Fixes microsoft/vscode-go#3152