In typical cases, this gives the same result as the existing logic.
On my system, "go env" gives the correct answer and the existing logic
does not.
I use the nix package manager to manage my
packages, including go. As a result, the go program in my PATH is a
symlink. If you go up two directories from it, you get the directory
containing all of my installed packages, not the go installation
directory. But if you call go env GOROOT, it prints the correct path.
In typical cases, this gives the same result as the existing logic.
On my system, "go env" gives the correct answer and the existing logic does not.
I use the nix package manager to manage my packages, including go. As a result, the go program in my PATH is a symlink. If you go up two directories from it, you get the directory containing all of my installed packages, not the go installation directory. But if you call
go env GOROOT, it prints the correct path.