Simon Krajewski

I've dug up the commit that checked typedef deprecation during typing: https://github.com/HaxeFoundation/haxe/commit/0eb30bd35509940a84f385c2a7352309aa007086 Unfortunately, it doesn't mention why I did that. The situation with overloads is a bit awkward because we...

So this check is needed for this very simple case: ```haxe class C {} @:deprecated typedef T = C; function main() { trace(T); } ``` The generated AST doesn't have...

I always do this from within vscode, and that works sometimes:

Actually I prefer a PR here because it's easier to reason about the code and see the failing tests, so I think this is a good initiative.

@basro Do you think this is something we could add to the inline constructor code somewhat easily?

Looking at this again, I wonder in which case this could even come up without being const-propagated away. If we statically know the null-ness and value of a local variable,...

This comes from a call to `TypeTools.applyTypeParameters`, but I can't immediately tell how it happens because there's a check in the Haxe code there to avoid this. Try adding a...

Unfortunately we can't tell what lookup it's actually failing on from the stacktrace. What I can say is that this comes from some init macro, but there's not much more...

Could you check that your haxe/std is in-sync with the compiler? You're probably using an old haxe/macro/Compiler.hx which tries to call an API that no longer exists. We should definitely...

So yes this is indeed a problem with `callMacroApi`, we can reproduce this easily: ```haxe class Main { static function main() { breakEverything(); } static macro function breakEverything() { eval.vm.Context.callMacroApi("oh...