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

futures: Write-then-transfer-read-handle does not work #1180

Open
alexcrichton opened this issue Feb 28, 2025 · 1 comment
Open

futures: Write-then-transfer-read-handle does not work #1180

alexcrichton opened this issue Feb 28, 2025 · 1 comment
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

Currently with the async runtime support for Rust if a future is created it yields a (reader, writer) end. They're both considered "local" until the reader is transferred away. If the writer has an ongoing write when the reader is transferred away then the write needs to be promoted from a local write to an intrinsic-based write. That doesn't happen today which means that the future basically gets stuck.

@alexcrichton alexcrichton added async Related to async/streams in the component model. gen-rust Related to bindings for Rust-compiled-to-WebAssembly labels Feb 28, 2025
@alexcrichton
Copy link
Member Author

I think specifically that today this behavior would trigger this abort because the state will be LocalReady after the write.

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