Rudy Ges
Rudy Ges
I think we'd only need to add support for this? ```haxe @:op(A==null) function isNull():Bool { ... } ``` As the other case can already be handled with a (albeit currently...
I like it too, but I'm really not sure about the use of `static` for this
Yeah it's the expected result as per the comment in the PR, but that makes no sense to me to allow that... I'd argue it's clearly not the expected result...
Workaround for empty array literal: https://try.haxe.org/#229CCBDE ```haxe @:from static macro function fromEmptyArray(e) { return switch haxe.macro.Context.typeExpr(e).expr { case TArrayDecl([]): macro new Foo(); case _: e; } } ``` Note that...
@Simn got anything against this?
Well there's `StringTools.hex` there too, so I guess that's where functions like this went until now, at least :/ I agree that it's weird to see functions with `Int` first...
cc @markknol who wrote most of the generator Hi Mark, do you have any preference here as to what license that code should be distributed under?
Happens because of a recursive dependency (`Tooltip` extends Box etc. up to `Component` and `ComponentBase` (and further) which use `TooltipManager` which uses `Tooltip`), and likely because of build macros trying...
You can also try disabling refactoring cache as you seem to have issues with it, and see if it helps: ```json "haxe.disableRefactorCache": true ``` In your vscode settings (`.vscode/settings.json`)
> Also, are you using Haxe version 4.3.7? According to the logs, that's 4.3.6