Juraj Kirchheim

Since there seems to be some activity regarding the compilation server, I thought I might try to revive this conversation a bit. > I don't know... diagnostics is just building...

I can confirm I have needed this on occasion. My workaround was to declare an abstract that would then do the mapping in its accessors. Not very concise to say...

FWIW here's a macro based implementation: https://github.com/back2dos/jsImport#jsimport---use-es6-imports-in-haxe Never actually used it in production, so I can't vouch for it, but I think it highlights the three different cases rather well...

It is trivial for the user to create threads with an event loop if required. If they fail to do so, they will get very predictable errors. If instead we...

> But suppose that you pass a callback that creates a timer (maybe indirectly) to a third-party library: in that case you don’t have any control on the thread that...

There are basically two libs available: - https://lib.haxe.org/p/hxtsdgen/ - this will produce definitions. - https://lib.haxe.org/p/genes/ - this will generate Haxe modules as ES6 modules and definitions as well. If you...

I don't know if it makes sense, but I wouldn't mind ;)

Hmm, after the changes to NEVER this seems to work fine.

As @nadako suggested, we should probably add `static public function never():Promise` to `Promise` and advertise that instead.

> As for haxelib run haxelib_cmd_, don't official haxelib libraries need to have a unique name? So haxelib_cmd_ wouldn't be needed. Your premise is definitely right, but amusingly your conclusion...