Zac Bergquist

We are working with tool maintainers to get everything updated to work with modules. Support for modules should gradually improve in the coming weeks. In the meantime, the best workaround...

@hyprnick is your `GO111MODULE` env var set? In vendor mode, you should leave that to `auto` or `off`. As long as it's not set to `on`, the tools shouldn't know...

@bensussman - hear you loud and clear. You're not alone - I too struggle to use go-plus with modules, and the story is the same in many other editors. The...

If you're watching this issue you could help by letting us know which features are not working with modules. As far as I can tell build/test, documentation, go to definition,...

Looks like a couple tests are broken, but otherwise LGTM.

I haven't seen that locally, though I admit it's been a while since I've tried. That sounds to me like a gopath or working directory problem.

@robbawebba If you want to do the work you're more than welcome to, I'm happy to help with the release.

Suppose we did allow setting the path to the go binary. What would you do about all of the other tools that this extension depends on (goimports, godef, gogetdoc, gorename,...

All binaries are not under `go/bin`. Many of them, but not all, are under `$GOPATH/bin` - but even that may change in the near future as the community adopts modules...

There's a new community maintained effort that will provide more granular control over which packages you use to satisfy the various IDE features: https://medium.com/@nazimboudeffa/atom-ide-community-to-replace-facebooks-nuclide-2c8c6aab5a32 Language servers are the direction everyone...