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

wasm: document that Tokio may use blocking ops #7207

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Darksonn
Copy link
Contributor

Closes: #7205
cc @binier

@Darksonn Darksonn added T-docs Topic: documentation A-tokio Area: The main tokio crate M-sync Module: tokio/sync T-wasm Topic: Web Assembly labels Mar 10, 2025
@github-actions github-actions bot added the R-loom-sync Run loom sync tests on this PR label Mar 10, 2025
//! blocking operations when more than one thread is involved. This means that,
//! for example, using a Tokio mpsc channel to send messages from a web worker
//! to the main browser context will not work, as the main browser context does
//! not support blocking operations.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not the case just for thread -> main thread, but other way around as well. So when sending messages from main thread to other threads.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just this. Otherwise looks good to me. Thanks @Darksonn!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-tokio Area: The main tokio crate M-sync Module: tokio/sync R-loom-sync Run loom sync tests on this PR T-docs Topic: documentation T-wasm Topic: Web Assembly
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Tokio channels can cause panic in wasm context, when using multiple threads
2 participants