[display] @signature completion and unnamed arguments

[nadako]

Haxe returns the following for @signature completion for callback types (and thus empty argument names):

"{"signatures":[{"label":"(:Int, :Int):Void","parameters":[{"label":":Int"},{"label":":Int"}]}],"activeParameter":0,"activeSignature":0}"

Not technically wrong, but looks ugly and makes VS Code go crazy:

Before @signature was a thing, I solved that by adding generic a,b,c,etc. names to unnamed arguments. Maybe we should do the same for @signature too. Thoughts? @Simn @Gama11

[nadako]

I guess I'll work this around by injecting argument names on haxe-languageserver for now.

[Simn]

I don't think Haxe should invent names here. It's up to the IDE how it wants to display this case.

[nadako]

In this case I'd argue that the output should be properly structured instead of spitting out weird concatenated strings, which is not much better than we had before format-wise.

[nadako]

People really shouldn't have to do this: vshaxe/haxe-language-server@942470d#diff-bdfa664c96d8ab764d530048de8ed45dR47

[Simn]

What's wrong with s.charAt(0) == ":" ? invented + s : s?

[Gama11]

That works for the parameters, but not the label:

"label":"(:Int, :Int):Void"

[Simn]

Yes I agree that requires more structure. If only we had JSON output for types...