fix(jco): async return writing for caller memory #1143
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
vados-cosmonic
force-pushed
the
fix(jco)=result-caller-memory-write-for-async-return
branch
from
6b66d10 to
80f9b92
Compare
This commit fixes a bug where the memory for writing to was being retrieved too eagerly (@ trampoline fn binding time), and was not available properly when performing async `task.return`s.
vados-cosmonic
force-pushed
the
fix(jco)=result-caller-memory-write-for-async-return
branch
from
80f9b92 to
dc323f3
Compare
Merged
via the queue into
bytecodealliance:main
with commit Dec 1, 2025
246b0a7
67 of 69 checks passed
vados-cosmonic
deleted the
fix(jco)=result-caller-memory-write-for-async-return
branch
Collaborator
|
🎉 The code in this PR was made available in the following release: |
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 commit fixes a bug where the memory for writing to was being retrieved too eagerly (@ trampoline fn binding time), and was not available properly when performing async
task.returns.