Rudy Ges

iirc that's about hashlink (or, to be more precise, sdl.hdll) being too old You might want to try hashlink nightlies

Same issue here, and I fail to use the workaround > Is there a way to work around it? Perform the keystroke on the server AFTER all other machines receive...

Do you know how we could repro this?

So this comes from exceptions in build macros triggered by another build macro. Not sure if this env kind business is correct; do you have a better idea there? Hopefully...

Testing this against eval debugger, with: * Original test (build macro + build macro + Context.parseInlineString) * Expr macro variant (expr macro + build macro + Context.parseInlineString) Note that for...

With this, I can get the stack displayed with compiler too; but not sure we actually want that ```diff diff --git a/src/macro/eval/evalExceptions.ml b/src/macro/eval/evalExceptions.ml index b3954e206..7140610ca 100644 --- a/src/macro/eval/evalExceptions.ml +++ b/src/macro/eval/evalExceptions.ml...

Usual random windows/macro failure is unrelated

> How can we define a new type and place it in an existing module please ? `Context.defineModule(cl.module, [newT]);` https://try.haxe.org/#7d2C7e94 (I know, this isn't intuitive at all :sweat_smile:)

> We should definitely disallow defining types into existing modules for Haxe 5, if we didn't do that yet. We didn't, but that should be easy enough: https://github.com/HaxeFoundation/haxe/blob/development/src/typing/macroContext.ml#L505-L513

Depends what you mean exactly with reorder build macros