This repository was archived by the owner on Jul 12, 2024. It is now read-only.
Fix #75: Use WebAssembly.JSTag as our exception tag. #103
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
This will allow to use the `JSTag` behavior for catching JS exceptions, while waiting for Node.js to catch up with V8 12.5. Luckily, we only need that for `TryCatch` and not for `TryFinally`.
This allows us to actually catch exceptions thrown by JavaScript code.
tanishiking
approved these changes
Apr 16, 2024
This was referenced Apr 16, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
First switch to using the legacy
tryinstruction to implementTryCatch, becausetry_tablewill only support catchingJSTagfrom V8 12.5. Luckily we don't have to do that forTryFinally!