[diagnostics] top down type inference

[ncannasse]

The following code creates a false positive Unresolved identifier FBone in diagnostics:

enum FxAttach {
    FBone(?name : String);
}

typedef FxOptions = {
    ?parent: FxAttach,
}

class A {
public function addFx(name : String, ?alias : String, ?addToFxs = true, ?opt : FxOptions) {
}
}

And another file:

class B extends A {
   ...
   addFx("Sparkles01", {parent: FBone("FX_Sparkles01")});
}

[ncannasse]

It can also create Arrays of mixed types are only allowed if the type is forced to Array<Dynamic> when you have Array of structures with optional arguments (which types correctly with top down type inference)

[Simn]

This will probably make me rethink how we handle diagnostics. I think it shouldn't be a display mode but use some other flag. That way we can treat it as normal compilation which just collects some additional data.

[Simn]

Interestingly, this still reproduces.