Possible bug in for in expression

Hej,

I noticed that and idk if it's a bug or what ? I think it's inconsistent since the 1st works

```haxe
class Test {
static function main() {
for( i in null ?? [] ){} // Ok
for( i in ( true ? [] : [] ) ){} // Ok
for( i in true ? [] : [] ){} // For expression should be 'v in expr'
}
}
```

No source files or tests are named. Start by running the minimal Haxe example from the issue and compare how the three for expressions are parsed; done means the inconsistent behavior is explained and the intended handling is covered by an appropriate regression test.

Written by the indexing model from the issue text.