Simon Krajewski
Simon Krajewski
Do you think we could move these additions to another file? gencpp.ml is a bit of a monster, and while I don't plan to refactor anything there, it would at...
This is pretty stupid. When unifying a type with a constrained monomorph, the compiler checks if the type fulfills the contraints, so it tries to assign it to each constraint....
Actually, this is a catastrophe: ```haxe class C { public var id:Int; } class Main { static function main() { final data = ({} : Dynamic); data.id = 0; test(data);...
Bisecting your example brought me to https://github.com/HaxeFoundation/haxe/commit/eda6551f2b4fa3f0b80088eb39869d1b83f811d7, which makes this problem even more ridiculous. It's kind of good news because it means that the regression is strictly related to Any...
Roughly in two years from now.
A bit more context would help here...
From my understanding one of the main problems with that PR was that it introduced target differences.
It is such a nice test case though... I can see how the logic _would_ work: ```haxe public static function equals(a1:Null, a2:Null):Bool { if (a1 == null && a2 ==...
That shouldn't work with `Array` because that's not what the data structure expects there. Maybe we can make it work if you actually pass the correct type (http://api.haxe.org/haxe/macro/FunctionArg.html) though.