You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed that in some cases, @:native and @:overload are placed in a typedef, so they won't really be used. A quick fix is to make the typedef an external class instead.
The text was updated successfully, but these errors were encountered:
This one is deliberate, unfortunately most of the time these cannot be converted to classes because we need structure type unification rules to apply, however right now haxe has no way to have a typedef with non-ascii fields, so some kinds of @:native-like approach is required there. Nakado has implemented support for @:native on typedef, if we're lucky it could arrive in 4.2, if it does then those fields with @:native will start working. There's no ideal work around and it's an ongoing talk in haxe on how best to resolve
See HaxeFoundation/haxe#9433
And HaxeFoundation/haxe#5105
I've noticed that in some cases,
@:native
and@:overload
are placed in a typedef, so they won't really be used. A quick fix is to make the typedef an external class instead.The text was updated successfully, but these errors were encountered: