8ac64289b3
I think this might have been broken by https://github.com/ruffle-rs/ruffle/pull/9506, but we didn't have proper test coverage. If we execute a 'coerce' opcode for a class while it's being initialized (which can happen by running a method from a static initializer), we'll be unable to resolve the ClassObject using `resolve_type`. This is the only case where this can happen - any superinterfaces/superclass will already be fully initialized when we're running a class initializer. Therefore, we can try to lookup the class from the `Domain`, and check if it directly matches the class of the object we're coercing (ignoring superclasses and interfaces). |
||
|---|---|---|
| .. | ||
| assets | ||
| build_playerglobal | ||
| macros | ||
| src | ||
| Cargo.toml | ||
| build.rs | ||