-
Notifications
You must be signed in to change notification settings - Fork 645
Use vscode-go without GOPATH #2458
Comments
That notification is about the extension's inability to find the tools. Are you suggesting that we remove the reference to GOPATH in that notification or not look at GOPATH for finding the tools? Even when GOPATH is not used by your projects, the default GOPATH would be ~/go which is where the tools will get installed to unless you set the |
Ah, sorry, my bad. I thought that no GOPATH is set by default. So, if not using GOPATH in projects, one shouldn't worry about it, right? |
Yes. I also agree that, that notification might be confusing to new users to Go, who might never had to think about GOPATH. Updated the messaging there to avoid reference to GOPATH with 21bab08 Thanks for reporting! |
Leaving the religious, almost cult-like defense of GOPATH aside, Go 1.11 allows people to use Go without a GOPATH using modules.
Yet when trying to use Go in VSCode, the following notification appears:
How should someone who isn't using GOPATH at all set up their environment in order to use VSCode for coding in Go?
Can the solution also be included here?
The text was updated successfully, but these errors were encountered: