Simon Krajewski

I acknowledge the problem but I don't think this is the solution. Imports are just tools to simplify type paths, so whatever problem you can create with imports you can...

I don't see how that argument (which I generally agree with) relates to the proposal. It's not like imports are inherited by the users of a library.

You correctly point that that there's a problem with `PosInfos` handling vs. rest arguments, but then your design doesn't explain how to actually resolve that in the context of your...

The detailed design section is supposed to be detailed. It's fine to have an incomplete starting point and work open questions out with the community, but for something as complicated...

Well, a compile-time-only feature is a long way from the proposed "fully work between all languages". I can't say that it sounds very attractive considering the complications it comes with...

Here's an example to make this easier to follow: ```haxe class Parent { public function new() { } public function test(t:T) { trace("Parent.test(T)"); } } class Child extends Parent {...

Dynamic dispatch is the thing that causes the child class function to be called even though the call is made on a reference typed as the parent class. If you...

Please note that this already works, relying on the `extern inline`: ```haxe class Test { function new(a:Int, b:Float) { } public overload extern inline static function create(x:Int) return new Test(x...

Actually, `extern inline` is just our way of saying "compile-time". The `extern` modifier has historically been used to express "this has to be inlined because it doesn't exist at run-time"....

Such a function would likely be needed for the full dynamic route, yes. But that's actually one step ahead of the other problem (case 2 from my example). In that...