Keegan Carruthers-Smith

I actually can't remember when we added that. But I suppose what is different about our implementation vs most language servers is we designed it to run in a datacenter...

I think hover/def didn't work before your godef change. Just that working may be sufficient. The workspace operations won't really work, since in general we need to know the package...

A more useful thing we could do is warn the user they are outside a GOPATH, and possibly provide an action to autoconfigure (find /src/ in a parent directory). I...

Supporting this properly seems error prone. It seems like if your `rootUri` was inside of `$GOPATH/src` then this wouldn't be an issue. Could you not open up your editor at...

Do we have code somewhere that resolves symbolic links? Assuming your `rootURI` is in the `GOPATH` I don't see why this wouldn't work, even in the case you mention @slimsag.

@ramya-rao-a we actually support an unofficial extension to LSP to specify the build tags to use https://sourcegraph.com/github.com/sourcegraph/go-langserver/-/blob/langserver/lspx.go#L41 So your initialize request would additionally specify something like ``` { ... "BuildContext":...

Note: The go tools team at Google is working on a language server which will support go/packages from the get go. Here is some more information on that https://go-review.googlesource.com/c/tools/+/136676#message-11c783bc9a9f6adf6119bbb85c89510fda25abe9 Unless...

If you are using vscode check out https://github.com/golang/tools/tree/master/cmd/gopls/integration/vscode

gopls is under active development by google's go tools team. What I linked to is likely early days, although I believe it is getting close to some sort of announcement....

I can't reproduce this, same version of go but on linux. I cleaned out my `go/src` and it compiles with what is just in vendor. I'm not sure if this...