go modules support

[lelvisl]

Hi!
Can you add vgo instead of go to the configuration?

[joefitzgerald]

Yes, this makes sense.

[lelvisl]

thx!

[lelvisl]

some news?

[zmb3]

No updates at this point. I'd like to wait to get more experience with vgo both personally and see more use in the wild to help inform what to build.

[g42sh]

+1

[hugollm]

I'm using go 1.11 and go-plus actually modified my project's go.mod to install the tooling.
Would make sense to install only on the workspace, right? Without modifying the project's dependencies.
Not sure if it's even possible to chose 🤔

[nick-phillips-dev]

I updated to go 1.11 and I'm having some issues with guru and godef. They are unable to find declarations based on the new cache system.

e.g.

[zmb3]

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 is to clone the module into your GOPATH and use go mod -vendor to populate a vendor directory.

[nick-phillips-dev]

@zmb3 Thanks for the response. I thought that would work as well but still getting the same error. Any thing else I can try?

[zmb3]

@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 a difference.

[nick-phillips-dev]

@zmb3 It is unset. I moved my project outside of the GOPATH once I upgraded to 1.11.