nsf
Well ok, I'll have a closer look at this package cache feature (sooner or later). Will let you know then, maybe it's possible to make gocode work with that cached...
I'm not going to do anything about it for now. Yeah, I know it sucks. Sorry about that. I really dislike this idea with package cache. It feels like another...
You don't need to ask me. If you can and want to make something that works well - do it. However, I may end up doing gocode v2 anyway one...
I said many times. Tools should work with source files only. The fact that "go/types" depends on compiled packages is a problem that needs to be solved. I don't care...
Using source files might be slower. But not by much.
This version of gocode doesn't work with go mod and is no longer maintained. You can try this fork: https://github.com/stamblerre/gocode, or some other fork.
It wasn't added by me there: https://github.com/melpa/melpa/blob/master/recipes/company-go. If it wasn't added by me, then it probably can be changed by somebody else also.
Gocode is no longer maintained, you can try this fork: https://github.com/mdempsky/gocode
Gocode is no longer maintained, you can try a fork, such as: https://github.com/mdempsky/gocode
Might help: https://github.com/nsf/gocode/issues/500 tl;dr: Go has package cache now, with 1.10 you can with hacks make gocode work, but in the long term who knows what happens next. Start looking...