You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 25, 2025. It is now read-only.
The overview mentions that subtyping is co-inductive, but it does not explicitly state that type section entries can reference later type section entries. If a reader were to extrapolate from Wasm's existing declarations-before-uses structure, they might arrive at the conclusion that type section entries cannot reference later type section entries and therefore recursive types are not allowed. Can we clarify this one way or another in the explainer?
The text was updated successfully, but these errors were encountered:
extrapolate from Wasm's existing declarations-before-uses structure
Yeah, in fact, I want to change this to def-before-use for types in this proposal, in order to avoid the recursive types rabbit hole for now. But that requires a few structural changes to validation and instantiation, which I haven't gotten round to implementing yet.
(Aside: Note that the property you describe only applies to the binary format, not to the abstract syntax or text format, where everything is considered recursive.)
The overview mentions that subtyping is co-inductive, but it does not explicitly state that type section entries can reference later type section entries. If a reader were to extrapolate from Wasm's existing declarations-before-uses structure, they might arrive at the conclusion that type section entries cannot reference later type section entries and therefore recursive types are not allowed. Can we clarify this one way or another in the explainer?
The text was updated successfully, but these errors were encountered: