nsf
@mdempsky it looks interesting, but I can't really test it out in "production", because we use gb. And as a result, I can't compare it to current gocode version. Test...
@zchee a new issue would be nice
@zchee I also probably won't take a look at it until the weekend. Well, depends on complexity.
`gocode drop-cache` won't do anything, it doesn't restart the server, it just drops in-memory gocode cache. After building new gocode version you need to restart the server, that's the important...
I have no explanation for that scenario.
The reason why I don't like relying on provided semantic analysis libraries is because gocode works with invalid go code. And what happens if these libs fail to handle some...
@sethgrid That error message of yours was removed in the commit 2735323. Try updating gocode: `gocode close && go get -u github.com/nsf/gocode` Or if your editor ships with its own...
@shurcooL > following the Go idiomatic style would make it easier for other people to do that What exactly in my style prevents users from contributing? They can't read snake...
@zchee just to be clear, this is not my style at all, I have no preference at the moment and can happily write javascript with camelCasing. Changing gocode to snake...
Input parsing errors like that are okay.