Simon Krajewski
Simon Krajewski
Yes I think that's what the "TODO: macro vs non macro" was about.
Huh, I also thought we merged this already...
The configuration is still missing, but I'd be fine with adding that "later".
Note that https://github.com/HaxeFoundation/haxe/pull/8426 was never merged, and I don't remember if HL ever fully passed these tests (our conversation there suggests that it didn't).
I'm kind of lying about the "only in return types" part here because there's also still the `Void -> ?` situation, which doesn't even go through the typeloader (which is...
That's debatable because `Void -> ?` is not the same as `(Void) -> ?`, and I think that's the only case where this is true.
Yes that's the question I'm asking, but in that case we surely should remove the old function type syntax entirely and not just this special case.
I'm being too hasty with that haxe.NoValue change because it's not actually a NoValue type, but rather a Unit type. Consider this: ```haxe class C { public function new() {}...
I'm making this the main coroutine PR with the following changes: * The logic from analyzerCoro.ml in #10128 has been moved and slightly cleaned up to coroToTexpr.ml. * The new...
Some notes on the transformation: If we have this: ```haxe @:coroutine @:coroutine.debug private function mapCalls(args:Array, f:CoroutineTRet>):Array { return [for (arg in args) f(arg)]; } ``` The transformer looks at this:...