Simon Krajewski

I'd be interested in seeing that POC!

I looked at this today and while it's easy enough to add some sort of flag, the problem is that we have to somehow turn it into `Null` at some...

I noticed that we were stuck on an outdated hxcpp branch. After updating this we now have green CI for cpp, which is a good baseline. As the next step...

Update: * *cpp* still works * *jvm* works as well now after [fixing a crazy inference problem](https://github.com/Aidan63/haxe/commit/d4431e49c42db0a03f6b476f2338d1cde32cefc6) * On *js*, the coro tests are passing too after [Aidan implemented a...

Update: * *cpp*, *jvm* and *js* still work. * *hl* works now too after reworking our data design in https://github.com/Aidan63/haxe/pull/33 * *eval* still fails until someone looks at #12176 *...

Easter update: * *cpp*, *jvm*, *js* and *hl* still work * *neko*, *python*, *php* and *lua* work too now after fixing minor issues for each of them (except python which...

Since I'm accidentally opening PRs from the coroutine branch already anyway, I thought I should give an update on the state of affairs! ## Lower level The lower level, which...

@kLabz Would be good to check this soon because it's a bit conflict-prone.

That looks like warning territory, mostly because I can imagine scenarios where a macro might generate this kind of expression. By using a warning, we give the user the option...

There are some controversies here in the context of abstracts. Consider this: ```haxe import haxe.ds.StringMap; function main() { var someMap:Map; trace(someMap is StringMap); } ``` Assigning `StringMap` to `Map` is...