Simon Krajewski
Simon Krajewski
I've looked at this for a bit to understand the problem. The `onTypeNotFound` functionality hooks into our internal `load_extern_type` feature. This was originally used for `-swf-lib` and later extended to...
Slightly related: Context.defineType could return a ComplexType which identifies the defined type.
Coming back to this, I realize that using `ComplexType` doesn't make sense here. `Context.onTypeNotFound` is about types, not type _instances_ which is what `ComplexType` represents. Even `TypePath` isn't correct because...
Somehow this is more awkward to implement than I anticipated. I'm working with this example: ```haxe import haxe.macro.Context; macro function macroReg() { Context.onTypeNotFound(path -> { return path == "NotExist" ?...
Doesn't haxelib already define `-D name=version` anyway? I see no reason to change anything in that regard.
Please post a complete example, in particular what `choice` is in that code.
What type is `Object`? I don't see where the `Float` comes from here, and the problem doesn't reproduce if I use `Dynamic`.
What Haxe version are you on?
I cannot reproduce this... Here's my attempt at reducing the example: ```haxe import haxe.Constraints.Function; @:dox(hide) @:noCompletion typedef ObjectType = Dynamic; @:transitive @:callable #if !haxe4 @:forward #end abstract Object(ObjectType) from ObjectType...
`code` exists on NativeException, which is the parent class of `Exception`. The solution is to rename your field.