Rudy Ges
Rudy Ges
Seems like I understood it backwards, sorry about that :confused:
You may want that `defined` var to be `@:persistent`?
Hmm yes it's a bit more involved than that. I've updated my PR #11159 and it does seem stable on nightlies at least, what I thought was random failures were...
No because it's a user/lib error without minimal repro so there isn't much we can do on compiler side
Couldn't both exist? Then adding `@:message.follow` would be a good start (not sure how useful @:message.message could be..)
Sounds like #9174 And yeah seems to be a hl-opt issue
This is just a warning, should be fine. What else is wrong ?
Maybe this can be used for that once I polish it a bit and release it? https://github.com/kLabz/hxdiff
Hello :) Yeah, links don't always work directly within haxelib, but they should be fine on github. You can find react-next documentation here: https://github.com/kLabz/haxe-react/tree/next/doc It's not first class support of...
It doesn't work with haxe 4's js.lib.Object because of `assign()` signature being (imo) wrong there: return type is set to `T` while `assign()` should be able to return an object...