Refactor CABI onto explicit stack-switching interface#637
Merged
lukewagner merged 1 commit intomainfrom Apr 22, 2026
Merged
Conversation
lukewagner
force-pushed
the
stack-switching
branch
3 times, most recently
from
40a9956 to
963688e
Compare
lukewagner
force-pushed
the
stack-switching
branch
from
963688e to
d753b0a
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
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.
This PR is pure CABI-spec-refactoring (no behavioral change) intended to simplify a subsequent PR in progress, but I found it kinda clarifying on its own, so I thought I'd post it in case folks were interested to review it or had comments.
The change is to factor out 4 functions (in a new "Stack Switching" section in CanonicalABI.md) which directly correspond to the Core WebAssembly stack-switching proposal's
cont.new,resumeandsuspend(whereresumeis split into 2 functions specialized to the 2 effect tags that are needed). These 4 functions then conveniently factor out and encapsulate all the Pythonthreadingplumbing from the existingThreadclass (that defines what a cooperative thread is), leaving only the semantically "interesting" bits inThread, which is nice. This change also helps clarify how one could implement Component Model concurrency in-terms-of stack-switching and how Component Model concurrency would compose with Core WebAssembly stack-switching-based concurrency.