RFC: Exception-safe event handlers #28
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
kjvalencik
reviewed
May 21, 2020
- Trim down the recap of RFC 25 - Remove the unnecessary `.upcast()` from the `schedule()` example - Mention that `try_catch()` could be useful in the implementation of `schedule_with()`
kjvalencik
approved these changes
May 29, 2020
dherman
added
the
final comment period
Contributor
Author
|
This RFC is entering final comment period! If there's no more significant discussion in the next 7 days, it will be accepted and merged! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This RFC modifies the design of RFC 25 with a solution to handling JavaScript exceptions that might get thrown during the process of launching the event handler.
Rendered RFC