Tweak how wasm runnable errors are handled #201
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
History: In order to support AssemblyScript's 'abort' handlers, Reactr's handling of Wasm
Callerrors was updated to take the result of the abort handler over the error from the Wasm runtime... but the consequence of that is when a runtime error happens but no abort handler is there to return a better error (such as in every other language...), theCallerror gets clobbered.This PR fixes that. It'll still prefer the nicer error returned by a registered
aborthandler, but if none exists, it'll fall back to the error fromCall.