-
Notifications
You must be signed in to change notification settings - Fork 87
Support Go Modules #46
Comments
@joefitzgerald thanks for creating this issue; you just beat me to it 👍 Linking back to the umbrella Go issue: golang/go#24661 @mdempsky FYI I intend to take a stab at adding support via |
I agree with @myitcv, we should use
I didn't use |
code below fix the problem.
|
working fork compatible with go 1.11 only |
Linking back to golang/go#24661 |
@ikgo thanks for taking a look at this. I stopped my investigation after speaking to @ianthehat at GopherCon. Someone in his team is already working on helping to fix |
@myitcv , is this project what you are referring to when you say:
It is listed on the tooling updates to support modules issue as Beta support, but didn't work for me. |
@lucastheisen it works fine here. How did you test it?
Also, make sure you editor is not setting the option to complete from source ( |
Yes; the changes in https://github.com/stamblerre/gocode will be made into a PR against this repo once they stabilise. |
@fsouza , I probably should have elaborated... It does download, install, and even run. But when used by vscode, it just hangs. If i
but found nothing. Any idea where that might be hiding for vscode? |
@stamblerre would you mind opening a PR here even if your work is not completely done yet? Would make it easier to follow along and tracking the progress. |
Just adding a note here so that it can be referenced from any issues that ask about the future of
More details on this and progress on Go tooling in general can be found in the golang-tools group. We are currently holding fortnightly update calls; notes from the first sessions can be found here: |
I think this issue can be closed. |
Context: I maintain Atom's
go-plus
package for go support. I know @ramya-rao-a is also interested in ensuringvscode-go
works well with go modules.There are a variety of failure scenarios for the current master version of
gocode
when using go modules support (in particular without using vendor mode).Over time, we may want to edit this issue to describe each of the failure modes and validate that they are fixed. My assumption is that the
cache
branch and a switch to usegolang.org/x/tools/go/packages
will both be required to get to completion. @mdempsky do you have specific plans here?The text was updated successfully, but these errors were encountered: