-
Notifications
You must be signed in to change notification settings - Fork 720
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
[Parser] Issues to resolve before switching to the new wat parser #6208
Comments
The new parser is now on by default, so closing this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
These are the issues (in no particular order) that need to be resolved before we can turn on the new wat parser by default:
v128.const
.array.new_fixed
length annotations mandatory.array.new_fixed
length annotations mandatory #6277$"..."
and the tests need to be updated to use it where necessary.local.set
andglobal.set
of tuple types correctly.pop <valtype>
, where the valtype can be a tuple type.[Outlining] The parser needs to support pops in control flow structures somehow.resume
#6295The text was updated successfully, but these errors were encountered: