-
Notifications
You must be signed in to change notification settings - Fork 74
Conversation
ca58ba0
to
66e2edf
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great explainer!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting read, thanks! Just one comment
I've read most of this PR but I need a day or two to chew on the part about nominal types and importing. |
Ok, I've looked through this again and refreshed myself on it. I think it is sufficiently baked that we should land and iterate on it, particularly around the nominal/structural subtyping issues. I don't see any reason to hold it up for that. So, lgtm, and sorry for the long delay on this. |
Thanks for the looking through this. Agreed we'll want to continue iterating on the structural/nominal design. |
The order of the `table.init` and `memory.init` immediates should be the index followed by the reserved byte (which is a placeholder for the table or memory index). This matches ordering of immediates in `call_indirect` (type index, followed by table index reserved byte).
This PR moves the stub "JS API" section out of MVP.md into a new MVP-JS.md that defines the JS API in terms of the JS Typed Objects proposal.