nsf
Just to clear that out. Gocode works with incorrect go code, I've added parser errors to the debug output to be able to investiage some weird cases, this case doesn't...
You're lucky that they work in some cases, nobody explicitly added support for these in any of the gocode's bundled editor plugins. :D Somebody needs to add that feature there...
Well by default gocode adds itself to the list, you can redefine the list to whatever you want I guess. The duplicates you get doesn't seem like they come from...
Gocode just tries to find the best completion results it can when you ask it to. If editor triggers completion at weird location it's a problem of an editor. Gocode...
Well in both of your examples it shows package-level autocompletion list, which means no context is considered. Gocode recognizes only few contexts: 1. when something before the cursor looks like...
Oh and what kind of completion do you expect after a string literal?
Yeah, gocode never returns an empty result. At least it shouldn't, maybe there are cases with incorrect syntax that you can make it do so, but the intentional logic is...
It's funny. Because that thing was written in 2012 and this is the first time it comes up. I am very interested in having a reproducable test case for this.
That code is rather incorrect Go, but I'll take a look at it on the weekend. Thanks.
Sorry for delay. Took a look at the example, it works on my machine. > it has to go in a function, of course Can you be more specific then...