fix(runtime): Do not lose exception in TS extends #1211
Merged
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.
SuspendExceptionScope
instead of clearing exceptionalloc
throws a JS exceptiontsconfig.json
and transpileTypeScriptTests.ts
PR Checklist
What is the current behavior?
Exceptions raised during TS extends call are lost and errors are difficult to detect.
What is the new behavior?
Exceptions raised during TS extends call are correctly thrown in JS and can be processed in a catch block or unhandled exception handler, or crash with a meaningful error.