Name WASI stream write permits - #217
Merged
jsturtevant merged 1 commit intoSep 11, 2026
Merged
Conversation
jsturtevant
added this pull request to stack #216
September 11, 2026 19:01
jsturtevant
force-pushed
the
jsturtevant-name-wasi-stream-limits
branch
from
September 11, 2026 19:07
d924139 to
147a838
Compare
Signed-off-by: James Sturtevant <jsturtevant@gmail.com>
jsturtevant
force-pushed
the
jsturtevant-name-wasi-stream-limits
branch
from
September 11, 2026 21:14
147a838 to
e709457
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.
Replace opaque WASI stream permit literals with named constants and source-linked documentation. This clarifies that the 4 KiB buffer permit aligns with WASI's blocking-write ceiling, while the 64 KiB filesystem permit is an implementation choice rather than a WASI requirement.