I'm going to use this issue to track all the bugs I find while working on the LSP
Error Reporting
block.setFriction(1, "");
This happens here
var b = a.map<string>(x => "a" + x);
is reporting as
Ambiguous call; multiple headers match:
<U@Arrays.zs:50:12>(projection: function(value: string): string): string[]
<U@arrays_map_2.zc:7:12>(projection: function(value: string): string): string[]
Could be reported as:
Ambiguous call; multiple headers match:
<U@Arrays.zs:50:12>(function(string): string): string[]
<U@arrays_map_2.zc:7:12>(function(string): string): string[]
There could be more cleanup, but I think removing the parameter names are a good start
Java reports this error as:
Ambiguous method call: both 'CompilerErrors.doThing(Function<String, String>)' and 'CompilerErrors.doThing(int[])' match.
General
I'm going to use this issue to track all the bugs I find while working on the LSP
Error Reporting
missing call argumentreported incorrectlyThis should be reported as
too many call argumentsor better1 parameter expecetd but 2 were givenThis happens here
The position should be reported in between the
()cannot find Xambigious callis too verboseis reporting as
Could be reported as:
There could be more cleanup, but I think removing the parameter names are a good start
Java reports this error as:
No operator in type position is incorrect when in call arguments

The position should be reported on the operator, instead of on the function call
Iterator errors are reported in the wrong place

General
ZenCode/CodeModel/src/main/java/org/openzen/zenscript/codemodel/definition/ClassDefinition.java
Line 46 in f325e2f