-
Notifications
You must be signed in to change notification settings - Fork 452
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
Batch of additional tests #287
Conversation
) | ||
|
||
(func $effects (result i32) | ||
(func "effects" $fx (result i32) |
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.
why should this be valid? i don't understand what two names for a function means
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 syntactic sugar for:
(export "effects" $fx)
(func $fx ...)
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.
Oh, thanks! I missed this part of the issue text...
lgtm |
The error messages don't match the tests yet (simd_lane.wast), that still needs to be worked out in WebAssembly#287.
- lane indices are u8 (nats), negative values are now parse errors ("unexpected token"), as are values with a positive sign +0x1 - changed a bunch of "expected i8 literal" to "unexpected token", in order to differentiate these syntax errors we probably need to change the parser to match on a bunch of EXTRACT_LANE <token we don't care about> - some "type mismatch" are now unexpected token Fixed WebAssembly#287
Fix a few typos in the MVP explainer
For starters, more tests for:
Also introduced a bit of sugar for exports. You can now write an export name as part of the function def itself:
or, if the symbolic name isn't needed, just
avoiding the tedious triple repetition of the name like before.