Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rust async: Closing a reader might raise a trap as it actually needs to close a writer #1184

Open
alexcrichton opened this issue Mar 3, 2025 · 0 comments
Labels
async Related to async/streams in the component model. gen-rust Related to bindings for Rust-compiled-to-WebAssembly

Comments

@alexcrichton
Copy link
Member

Today if you create a (reader, writer) pair for streams/futures if the writer is dropped before the reader then when the reader is dropped it'll use the close-readable intrinsic. I think this will raise a trap thoug as it's actually a writable end, not a readable end.

@alexcrichton alexcrichton added async Related to async/streams in the component model. gen-rust Related to bindings for Rust-compiled-to-WebAssembly labels Mar 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
async Related to async/streams in the component model. gen-rust Related to bindings for Rust-compiled-to-WebAssembly
Projects
None yet
Development

No branches or pull requests

1 participant