3 ms·

I thought 1.12 was the release that was going to include a go team maintained language server. Is 1.13 a reasonable time frame to expect it to land? When 1.11

I thought 1.12 was the release that was going to include a go team maintained language server. Is 1.13 a reasonable time frame to expect it to land? When 1.11 came out I started using a project with modules, which caused many go tools pulled into vscode to completely break. One of those tools was the sourcegraph language server: https://github.com/sourcegraph/go-langserver#go-language-server- https://github.com/sourcegraph/go-langserver#go-language-ser... Bingo (referenced in above link) seems to at least work, but seems to be a bit slow sometimes. I am assuming at this point that this change set is just laying the foundation: https://go-review.googlesource.com/c/tools/+/136676#message-11c783bc9a9f6adf6119bbb85c89510fda25abe9 https://go-review.googlesource.com/c/tools/+/136676#message-...

icholy 8y ago
I've held off of using modules for this reason. I can't take that productivity hit.
SamWhited 8y ago
Something like this likely won't be a part of a release or on the Go release schedule. If it's made, it will be a separate tool with its own release schedule (I suspect).
zegl 8y ago
There is a language server merged into the "tools" repo [1], so something is definitely in the works! 1: https://github.com/golang/tools/tree/master/internal/lsp https://github.com/golang/tools/tree/master/internal/lsp
- jpeeler 8y ago
  I see now about a month ago it was renamed gopls, at least for the user facing command. https://github.com/golang/tools/tree/master/cmd/gopls https://github.com/golang/tools/tree/master/cmd/gopls There's also a vscode directory, so maybe it's worth checking out. I'm guessing it's too soon, but at least I know where to look more closely now.