Simon Krajewski

Thank you for the detailed instructions! I can reproduce this on latest Haxe, so this should be quite interesting to figure out.

One thing that's immediately strange to me is that the initial state of the application is already erroneous, which means that the compiler won't cache anything in the first place....

That fails while writing out the `LineNumberTable`. The specification says that it's alright to have multiple of those, so I guess I can just split them if they get too...

Actually this isn't going to help because the actual values are still 16bit, so any line or code offset beyond that would still error. In fact, from reading a bit...

```haxe macro function make() { var num = 21845; var acc = [for (_ in 0...num) macro call()]; return macro $b{acc}; } @:pure(false) function call() {} function main() { make();...

I don't consider this a bug, it's a limitation. The only course of action here would be to somehow split up functions that are too big, but that would come...

This seems sensible. Could you elaborate on that special case, because all I'm seeing is ??????...

By the way, there's something wrong with `Host.localhost()`. I'm getting `String should be sys.net.Host` on JVM because it's defined as `public static function localhost():String`. This code does compile on eval,...

After thinking about this again, I'm not sure anymore if this is really a good idea. We would muddle the concept between "optionality" and nullability. The feature is called null...

My problem here is that I acknowledge the problem you're describing, but I still don't think inferring fields as optional is correct when they are subject to _null_-coalescing. However, I...