Skip to content

Conversation

@lukewagner
Copy link
Member

The 0.3 updates to wasi:http in wasi-http/#143 helped highlight the fact that the reasoning for why we want to be able to pass an error-context into stream.close-readable and get an error-context out of stream.read applies just as well in the opposite direction (to stream.close-writable and stream.write, resp.). This PR basically just removes one of the few asymmetries from the otherwise-quite-symmetric read/write code.

@lukewagner lukewagner merged commit a52fc75 into main Feb 24, 2025
2 checks passed
@lukewagner lukewagner deleted the symmetric-error branch February 24, 2025 19:47
alexcrichton added a commit to alexcrichton/wasm-tools that referenced this pull request Feb 24, 2025
Account for changes in WebAssembly/component-model#446 and update the
validation here to expect two `i32` parameters instead of only one.
alexcrichton added a commit to alexcrichton/wasm-tools that referenced this pull request Feb 24, 2025
Account for changes in WebAssembly/component-model#446 and update the
validation here to expect two `i32` parameters instead of only one.
alexcrichton added a commit to alexcrichton/wasm-tools that referenced this pull request Feb 25, 2025
Account for changes in WebAssembly/component-model#446 and update the
validation here to expect two `i32` parameters instead of only one.
github-merge-queue bot pushed a commit to bytecodealliance/wasm-tools that referenced this pull request Feb 27, 2025
Account for changes in WebAssembly/component-model#446 and update the
validation here to expect two `i32` parameters instead of only one.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants