This repository was archived by the owner on Apr 25, 2025. It is now read-only.
Understanding subtyping matching #539
Replies: 1 comment 1 reply
-
Reference 1 is also a defined type, not the abstract heap type |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I'm running into a problem when testing my runtime against the wasm test suite, specifically this test:
gc/test/core/gc/ref_test.wast
Line 276 in e5af649
I'm currently matching these two types as I've made the following assumptions:
Looking at the matching logic from the reference interpreter it would appear that these should match:
gc/interpreter/valid/match.ml
Line 78 in e5af649
So I'm guessing maybe Reference 1 should not be a abstract heap type of struct? I get this after substituting the reference type embedded in the instruction 🤔
Somewhere I'm going wrong and I feel like I should be comparing two defined types and thus would be not matching because the structs don't match
Beta Was this translation helpful? Give feedback.
All reactions