-
Notifications
You must be signed in to change notification settings - Fork 830
Proper error handling in add* and get* methods #1570
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
Conversation
|
Also added a line to customize how we exit on fatal errors - instead of letting node call |
jgravelle-google
left a comment
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.
lgtm
|
I finally found time to rebase this and fix the test issue. The problem there was that the |
…r atexits in binaryen.js, we just don't want those warnings cluttering us up
|
I found a way to work around the test issue, by just disabling the atexit() assertion messages in binaryen.js, instead of disabling all assertions in non-optimized builds. |
See #1479 (comment)
Also a one-line readme update, remove an obsolete compiler (mir2wasm) and add a new one (asterius).