Skip to content

Add some typechecking tests #289

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

Merged
merged 1 commit into from
May 14, 2016
Merged

Add some typechecking tests #289

merged 1 commit into from
May 14, 2016

Conversation

binji
Copy link
Member

@binji binji commented May 13, 2016

No description provided.

@binji
Copy link
Member Author

binji commented May 13, 2016

I don't understand this error:

.......................................string:1.1-1.43: no module defined
F.

The tests pass locally for me; am I holding it wrong? :)

@rossberg
Copy link
Member

That's because the test runner tries to convert every test to binary, and that fails if there is no module defined. Adding a dummy (module) should fix it.

@rossberg
Copy link
Member

Other than that, lgtm.

@binji binji force-pushed the typecheck-test branch from 9c68863 to 248d06c Compare May 14, 2016 17:31
@binji binji merged commit 6e6ec28 into master May 14, 2016
@binji binji deleted the typecheck-test branch May 14, 2016 19:04
ngzhian added a commit to ngzhian/spec that referenced this pull request Nov 4, 2021
- 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants