* Function renames * Function references across packages * imports on save
Some of this can be fixed by restarting gopls (experimental) ever 20m: https://github.com/Microsoft/vscode-go/wiki/Go-modules-suppo...
From the v0.3.0 release notes[1]:
Workspace-scoped references, rename, and go to implementation. These features use your workspace root as the search scope, so behavior will vary based on the directory you open in your editor
[1] https://github.com/golang/go/issues/33030#issuecomment-51015...
I just got work to pay for a GoLand licensed for me. The VSC experience was slower, more RAM hungry and not as full featured, so it didn't really make sense to stick with.
That was resolved a while ago. Godoc supports modules[1]:
For those who are following this issue because you are waiting for module support in the godoc command (golang.org/x/tools/cmd/godoc), please note that it has been implemented in the latest version. See issue #33655.
[1] https://github.com/golang/go/issues/26827#issuecomment-55194...
I'm new to go (and so far enjoying it). I haven't use modules yet. How do they break IDE support ? (using Goland here)
Edit:
Go modules were not welcomed and godep was supposed to be the official dep manager: https://twitter.com/_rsc/status/1022588289461743617
Godoc is broken because of it and Rob Pike doesn't like it: https://github.com/golang/go/issues/26827#issuecomment-51584...
VScode with gomodules is still bad even with gopls restarting every 20m: https://github.com/Microsoft/vscode-go/wiki/Go-modules-suppo...