Repository navigation
Document rethrowRetire for compiled extensions - #20
Merged
Merged
Conversation
Mistium
force-pushed
the
compiled-rethrow-retire
branch
from
November 1, 2026 07:16
d27c334 to
44e35a9
Compare
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.
Stacked on #19.
This documents
rethrowRetire, a new helper in the compiled extension context from MistWarp/scratch-vm#41. After the TurboWarp compiler performance port,stop allordelete this cloneinside a custom block stops compiled code by throwing. An extension that wrapsbranch()or an input intry/catchhas to rethrow that signal, or the code after itscatchkeeps running.compile/compFunctable now listsbranch,yieldLoopandrethrowRetireonutil.The new section in the light theme.
The same section in the dark theme.