You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looks like nsf/gocode is official no longer being maintained.
It also is much more aggressive than its fork (https://github.com/mdempsky/gocode) about building/compiling. In large codebases this can cause a spectacular amount of processes to be started 30+ go builds of the same files). I'm happy to provide more detail here, but didn't want to distract too much from the other issue.
I saw there was a PR introducing the fork, but that some additional configuration was required for it to work. As a result, I believe it was reverted.
Is there anything that can be farmers out to volunteers for that task? I'd be happy to help.
The text was updated successfully, but these errors were encountered:
What did you do? (required. The issue will be closed when not provided.)
Checked the repo below:
nsf/gocode@9f3c24f
Looks like nsf/gocode is official no longer being maintained.
It also is much more aggressive than its fork (https://github.com/mdempsky/gocode) about building/compiling. In large codebases this can cause a spectacular amount of processes to be started 30+ go builds of the same files). I'm happy to provide more detail here, but didn't want to distract too much from the other issue.
I saw there was a PR introducing the fork, but that some additional configuration was required for it to work. As a result, I believe it was reverted.
Is there anything that can be farmers out to volunteers for that task? I'd be happy to help.
The text was updated successfully, but these errors were encountered: