Simon Krajewski
Simon Krajewski
I guess `cl_constructor` would have to go in there too...
[You're not lying...](https://github.com/Simn/haxe/commit/916f860859c5534ba5111e2a101ccc164fe0e2ab)
It's a limitation due to our architecture. But acknowledging that and addressing it are two separate things here.
Does anyone know what the status is here? We fixed some related things.
Reopening this because I'm currently working on the typer pass system, and I'd at least try to address this. Nadakos example is very nicely isolated and should allow some investigation.
That's a apply type parameters call with something that's not a type parameter. Not sure if this is a user or a Haxe issue, but we should make this fail...
The first case is a matter of detecting `if (true)` in particular, which should be easy. The second one requires merging all loop exits, i.e. all `break`s. This will also...
Interestingly, the analyzer doesn't const-propagate the `==` case either: ```haxe class Main { @:analyzer(full_debug) static function main() { var value:Int = 0; while (true) { var random = Math.round(Math.random() *...
That one seems much harder because it requires some sort of post-condition handling, and real code-flow analysis. The analyzer could probably figure it out but the var init checker won't...
> > The first case is a matter of detecting `if (true)` in particular, which should be easy. > > `if (...) {value = ...;} else {value = ...;}` is...