Simon Krajewski
Simon Krajewski
> Another workaround that seems to work for me is to fence the `@:generic` meta, while keeping `static public macro function parse()`. > > ```hx > #if !macro > @:generic...
This does give a warning on all targets. Please note that on try.haxe you might find it in the "Compiler output" tab. Eval is probably a special case in this...
I think your analysis is correct. The code you point out makes no distinction between `Var` and `Method`, so any instance field that has a function type would be considered....
This is some kind of setup problem on your end, please refer to http://community.haxe.org if you have further trouble!
@ncannasse: How do you feel about this? It seems correct to me to infer `null` as `Null`, but I'm somewhat concerned about inference differences that come from different typing order:...
That's the conclusion I arrived at too. It's not really different from assigning Int and Float values where the order matters as well. I think we should infer `Null` now....
There's some inference problem in the neko standard library of all places. I'm dodging this for now, but will have to check what's going on there and if it happens...
Yes that was the problem I'm dodging now. Although now there's some new problem...
@jdonaldson: Any interest in looking into that?
Where are we showing email addresses publicly? Because I don't think we should do that...