Zeta
Zeta
Even JavaScript has atomics now, no reason why Haxe shouldn't. Supported targets: - Hxcpp (https://github.com/HaxeFoundation/hxcpp/pull/985) - Hashlink (https://github.com/HaxeFoundation/hashlink/pull/523) - Java/JVM - JavaScript The hashlink unit tests fail in `TestException` when...
The JIT implementation is based on what GCC emits for it's intrinsics. The C implementation is copy pasted from what I did for hxcpp. See https://github.com/HaxeFoundation/haxe/pull/10610
See [HaxeFoundation/haxe#10610](https://github.com/HaxeFoundation/haxe/pull/10610)
The FNF modders want transparent windows. The implementation has not been tested.
Most things should be handled now. Marking as draft because constant buffers aren't implemented yet. On D3D11 there's enough information available about the shaders, but not on OpenGL. More specifically...
This changes the behaviour of `lime build ` by respecting the users preference for HL or Neko (current behavior is to force Neko). Also changes the default target for cross-compilation...
A replacement for that `?pos:haxe.PosInfos` magic. [Rendered proposal](https://github.com/Apprentice-Alchemist/haxe-evolution/blob/proposal/track-caller/proposals/0000-track-caller.md)
This fixes a bug where typed exprs coming from macros won't have their types properly substituted in generic functions. A simple example is ```hx function main() { foo(0); } @:generic...
Closes #11689
```hx function foo(val:hl.Ref) {} function main() {} ``` Compile with `haxe -m Main -hl out/main.c`. Error message: ``` ERROR (unknown position) | Invalid_argument("output_value: functional value") ``` Tested with commit https://github.com/HaxeFoundation/haxe/commit/c850b652a1f69dbbc0fd903da04419eeda81b225...