Juraj Kirchheim
Juraj Kirchheim
When generating status codes from error codes, it should be `% 200 + 400`, to make sure it always comes out as an error code. It will thus be possible...
This is just an idea. One alternative would be to have a `StrictClient` (or something more aptly named) that does this.
Ensuring the same runtime structure for anonymous objects of the same compile time structure generally makes life easier for JITs. It also has a couple of adverse effects though, so...
Some internal objects like subscriptions could be pooled (at least on platforms that erase generics).
AFAF: https://try.haxe.org/#52ff1319 ```haxe @:using(Test.MyEnumUtils) enum A { VA; VB(isX:Bool); } abstract B(A) from A { @:to function toString() return this.toString(); } class MyEnumUtils { public static function toString(v:A) return switch...
[Minmal example](https://try.haxe.org/#0257D916) ```haxe import haxe.ds.Option; class Test { static function main() { var a = [ Live, Offline({ vct: None, ot: Some('foo') }), Offline({ vct: Some('bar'), ot: None }), ];...
Because TypeDefinition lacks a few features (mostly import and using), it would be nicer to be able to call defineModule and have the compiler check again whether the type is...
In haxe 4 these all used to be optimized, while in haxe 5 it [only seems to work for `Dynamic`](https://try.haxe.org/#38C167cD): ```haxe function main() { var v:Dynamic = 0; trace(Std.is(v, Int));...