Emi

@keegancsmith I imagine this is a bigger issue once you consider that a monorepo is a GOPATH, so this means the langserver doesn't work very well in an editor environment...

@ramya-rao-a To clarify what @keegancsmith said above a bit, you would specify the `initializationOptions` like this: ``` "initializationOptions": { ...your existing initialization options... "BuildContext": { "BuildTags": ["integration"] } } ```...

https://github.com/sourcegraph/go-langserver/pull/305 should ultimately fix the `PANIC` issue once merged I think

+1 for goreleaser, looks neat! Of course it's also very easy to roll our own as I did in src-cli using gox: https://github.com/sourcegraph/src-cli/blob/master/.travis.yml I think it should be easy to...

From my discussion with @nicksnyder -- we settled on him using the specs I wrote above _and_ limiting the results on the frontend temporarily (b/c Go/Java LS do not respect...

What did you have in mind? (maybe link to an existing contributing file you like?) In general, we don't have any special contribution rules or anything -- it's the same...

I realize now our readme file doesn't describe how to e.g. develop go-langserver with Visual Studio Code. If that is primarily what you are thinking of here, I think it'd...

Got it, that makes sense. 😃 > Of course, we wouldn't need something so big as the Kubernetes Contributors Guide, but having some sections describing best practices and environment setup...

@chandradeepak To clarify what @keegancsmith said above a bit: `find references` with the language server is more slow if your code imports a lot of Go packages, or if the...

In order to fix this issue, we will need to switch over to using the new [golang.org/x/tools/go/packages](https://godoc.org/golang.org/x/tools/go/packages) package. Almost all of the CPU and memory usage from go-langserver comes from...