Explore setting gogetdoc as the default doc tool on new installations

[ramya-rao-a]

We added support for gogetdoc last November and it solved a number of issues in the Go extension

gogetdoc is not yet the default option.

Once there is a resolution on #667, we can look into making gogetdoc the default option.

[tayhalla]

Fwiw - I had the GoToDef and click to def fail for me randomly. I followed all these other issues and nothing resolved it.

Finally, I realized homebrew updated my go version doing a large update. The tools VSCode installed during the initial use of vscode-go were out of date. Going to the VSCode commands and running Go: Install Tools fixed everything for me.

[labregowski]

Hi.
@tayhalla, sorry for my ignorance. I just installed VSC yesterday. How do I go to VSCode commands :D?
Thanks in advance

[atishpatel]

Just a report. I switched to gogetdoc and it seems to be working pretty slow (~2 secs), but I had to switch because I kept getting godoc not found error. 🤷‍♂️

[otterley]

I support making this change as the default. My out-of-the-box setup on a new Mac did not work with the latest versions (VS Code 1.29.0, Go extension 0.7, Golang 1.11.1) until I switched to gogetdoc.

[ramya-rao-a]

Now that there is active development on an official language server for Go via gopls, we will soon be suggesting to use it for most language features including Go to definition, signature help and info on hover.

Therefore, there will be no further work in investigating whether gogetdoc should be the default or not for the go.docsTool setting.

For more on language server integration with this extension, please see Go language server

To go a feature request for gopls, use the Go issue tracker