CM-4: one-sentence question formulation + hold-rule protection decomposition - #31
Merged
Conversation
…rule actually protects
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
1 participant
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.
Follow-up to #29, distilled from operator discussion. Adds to
spec-amendment.md: (1) the issue-title-level formulation — should a callback-lifted task in its post-return phase, suspended mid-frame, still gate same-instance entry (doesexclusive_threadoutlive resolution) — plus the note that the window covers any mid-frame park (sync builtins, sync-lowered async-typed imports incl. host functions, yields), all viaThread.block_internal; (2) the two-class decomposition of what the hold rule actually protects at such a point — application state (thin: real only for all-async-export components, since non-async exports barge past the lock) vs shadow-stack LIFO (real, unconditional, but a property of the task's own continuation code — hence priced as the Invariant #3 toolchain contract, not an instance-wide mutex); (3) rules out the trap-on-post-return-suspension third option against both corpora and the producer idiom.Docs-only.