-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parse the remaining sections from the binary WASM format #67
Conversation
e3ad34e
to
eebb271
Compare
eebb271
to
ba6e74d
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.
This looks good!
I agree with commentary about exports --- they look fishy and don't respect the namespace structure of modules --- however, that is something that we can address down the road.
syntax DefnResult ::= parseElem1(BytesWithIndex) [function, total] | ||
| #parseElem1a(BytesWithIndexOrError) [function, total] | ||
| #parseElem1b(IntsResult) [function, total] | ||
rule parseElem1(BWI:BytesWithIndex) => #parseElem1a(parseConstant(BWI, b"\x00")) |
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.
This is a small nit; I would prefer to our existing macro for this constant to help readability a bit.
Also, right now, the macro is called ELT_KIND
, but I think it might be better to call it ELT_KIND_FUNCREF
--- I didn't pay close enough attention to realize that element kind reduces to a type.
The same applies to the other uses of the zero byte.
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.
Done.
7ccb9fd
to
96bf72d
Compare
Closes #62