nsf
@kovetskiy no, due to unpredictable schedule I don't see how it's possible. I might be coding it every day for a week and then doing zero progress for a few...
Well, listen, when and if I have some code to show, then we can talk about collaboration. It's pointless to collaborate over something that doesn't even exist yet. I don't...
Added a link to "mdempsky/gocode" to README.md. Hopefully @mdempsky, you don't mind.
Although I understand that you don't have a magic fix for "package cache" problem yet. The chance that you'll have one is much higher than on my end. The "-source"...
Sorry for message spam, but to clarify a bit what I think here. Basically in short term if new Go binary packaging changes affect you (e.g. you don't use alternative...
why should it work? 128 byte is here: ```go package main import ( "fmt" "net" "os" "strconv" "syscall" ) var str string func main>>>>>#
I can make a flag which disables that feature on the gocode side.
Added in https://github.com/nsf/gocode/commit/416643789f088aa5077f667cecde7f966131f6be. The option is enabled by default to keep backwards compatibility. Try disabling it, maybe it solves your problem.
No it's a bug. https://github.com/nsf/gocode/issues/385
It's a wrong assumption on your side. There is this thing called file cache. Most operating systems do have one. OS caches recently read files in-memory in case if you...