Simon Krajewski
Simon Krajewski
If you get a hold of a scenario where this reproduces, please try adding `tctx.m
I suppose we should finally disallow type parameter Void for Haxe 5. See #3463.
I just tried this and only get the error message once. Could you check again?
Any idea what's the status here?
I'll have to check all this again, I thought this `name_pos` business was mostly for enum instances, where we can't access the value from Haxe anyway. But yes I'd like...
I think this is a cache-problem with `ctx.g.functional_interface_lut` not being populated when modules are restored from the cache.
I'll fix this on #11544 because that's easier. A test would be good, too.
The delayed nature of constraints check doesn't play along very well with the TAnon mutability changes. A unification may or may not change a Const anon structure to Closed before...
With #9549 both cases fail in the same way. ... now I just have to understand if that's good or bad.
This very likely comes from https://github.com/HaxeFoundation/haxe/pull/11019. The `Runnable` interface used to be hardcoded, now the compiler relies on checking all known types. The behavior here suggests that the compiler either...