Improving scoring: post unexpected results here about fuzzyautocompleteplugin HOT 11 OPEN

Reported in #34, both iOS and OS X, lowercase ns, expected NSArray/NSString/..., does not go away.

Can be resolved by decreasing Context and increasing Learning parameter (e.g. to 0.25, 0.75).

from fuzzyautocompleteplugin.

When typing if (to begin an if/else statement), I get these results:

from fuzzyautocompleteplugin.

@wookiee I cannot see neither if nor ifelse on your list. If that is the case, it is not a matter of scoring (as mentioned in the first post).

Please open a separate issue with more details (on when and where in the code it happens) if with plugin disabled you get if and ifelse on the list, and with plugin enabled you don't.

If the if and ifelse are still missing after disabling the plugin (e.g. you get 'No completions') then Xcode does not think you can insert an if statement there. This happens for me when I type if inside [] where it does not make sense. Xcode might also be confused for some reason (e.g. indexing, runaway brace, syntax or other error in the same file). Please confirm wether the issue actually persists.

from fuzzyautocompleteplugin.

I see the issue with the literal BOOLs almost always. Usually it's NO that isn't marked appropriately (I've never used NSOSF10OperatingSystem, except perhaps by accident), but sometimes YES gets marked down as well. While I can deal with this fairly easily, it seems to annoy some of my coworkers enough they've stopped using the plugin.

(Weird. As soon as I was done writing this I turned the visible scoring on to see if I could get some better data, and now it completes YES/NO correctly every time. NSOSF10OperatingSystem still scores absurdly high for something that has never been used. Perhaps I've gotten used to manually correcting the BOOL literals and the appropriate values now score higher.)

from fuzzyautocompleteplugin.

I often have problems writing numbers. In 99% of the cases i just want the number and not a random function that has a number in its name. Suggested fix: Maybe have just the number as the default autocomplete, then functions under it.

from fuzzyautocompleteplugin.

Swift booleans are always a problem, both "true" and "false" get replaced with DYLD_BOOL types "TRUE" and "FALSE"

from fuzzyautocompleteplugin.

Same problem of @akolov .. Booleans are really annoying.

Why there aren't language builtins in completions?

Ty ;)

from fuzzyautocompleteplugin.

Other Swift issues include parameter names (doesn't seem to recognize that I'm typing a name and tries to complete for everything) and closure capture parameters (same issues). Really annoying to have to escape out of the completion menu.

from fuzzyautocompleteplugin.

Are there any news on this issue (booleans in particular) ?

from fuzzyautocompleteplugin.

Are you actually missing the Bool true/false from the completion list? Is it also the case with plugin turned off?

Without importing Foundation I get only Bool true and false.
With Foundation I also get (among other things) Int32 true and false, and the DYLD_BOOL uppercase TRUE and FALSE but those loose in terms of scoring with case matching lowercase versions (unless I actually type it uppercase).

from fuzzyautocompleteplugin.

I have same suggestion with @haaakon , @slazyk can you improve it? please.
Thanks.

from fuzzyautocompleteplugin.