Simon Krajewski
Simon Krajewski
This comes from the display-texpr processing calling `handle_import_hx` again, which doesn't account for the possibility of the module in question being cached already. This might actually be a more general...
That might be undefined behavior depending on what that `Executor.create` function does exactly.
Could you link that function or paste its implementation?
Ah yeah, `trace` is quite special. Not sure what we can do here without some sort of hack. But I agree that this is pretty unfortunate.
This is a variance situation: ```haxe import haxe.Constraints.Function; abstract Event(Int) { } function main() { var e1:Event; var e2:Event Void>; e1 = e2; // () -> Void should be haxe.Function...
Shouldn't the order of arguments follow JS here? Also, I hate JS.
If everyone agrees that the jsImport approach is good, I can port that to the compiler. I don't think we have to reinvent any wheels here.
This is mostly a design question because I'm not sure if `@:forward` should pick up additional semantics like that, or if a different metadata should be used instead.
```haxe class Main { static function main():Void { var arrayNullInt:Array = [0, 1]; var arrayInt:Array = [0, 1]; arrayNullInt = arrayInt; // oh no trace(arrayNullInt); } } ``` Oh hey...