-
Notifications
You must be signed in to change notification settings - Fork 87
go-langserver + gocode integration #63
Comments
@anjmao Sounds worthwhile of a PR to me. |
I'm a bit confused about gocode.
As autocompletion is one of the most useful features (at least for me) would't it make sense to move gocode to some organisation so we have official place for development instead of having fork of fork of fork? Currently I even don't know to which repo should I contribute if I want to fix something. |
@anjmao please see #46 (comment) |
As @myitcv mentioned, the Go team is currently working on a language server that will replace gocode. I will maintain mdempsky/gocode for now, but I don't think we will be making any major changes, and we don't want to expose any APIs that others may depend on. I'm not sure how go-langserver stays consistent with the internal/suggest API, but at this point, I would say that if you want to make a contribution to both repositories, you will have to make 2 PRs. I'm sorry about the state of things--it will be improved soon! |
@stamblerre Very glad to hear that an official language server is in progress. When will the early beta version be released? I'm looking forward to it! |
@imjustfly we don't have any specific dates set yet, but we will definitely publicize it when there is a beta version. |
Hi, recently I updated go-langserver to use gocode suggest API. go-langserver is directly using internal/suggest api since it doesn't need to run daemon with server-client.
Here are few problems I see.
My suggestions:
internal/suggest
to publicpkg/suggest
.go get github.com/mdempsky/gocode/pkg/suggest
.@mdempsky
I could make PR for this change.
The text was updated successfully, but these errors were encountered: