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

Document how to use channels between async and sync #2495

Closed
Darksonn opened this issue May 6, 2020 · 1 comment
Closed

Document how to use channels between async and sync #2495

Darksonn opened this issue May 6, 2020 · 1 comment
Labels
A-tokio Area: The main tokio crate C-maintenance Category: PRs that clean code up or issues documenting cleanup. M-sync Module: tokio/sync T-docs Topic: documentation

Comments

@Darksonn
Copy link
Contributor

Darksonn commented May 6, 2020

When communicating between sync and async code, you typically want to use the channel type that corresponds to where the receiver is. That is, unless you are using a bounded channel. I would like to discuss these concerns on the sync module.

@Darksonn Darksonn added E-help-wanted Call for participation: Help is requested to fix this issue. T-docs Topic: documentation E-easy Call for participation: Experience needed to fix: Easy / not much C-maintenance Category: PRs that clean code up or issues documenting cleanup. A-tokio Area: The main tokio crate M-sync Module: tokio/sync labels May 6, 2020
@hawkw
Copy link
Member

hawkw commented Jul 1, 2020

I think this was finished in #2600 and #2624, right?

@Darksonn Darksonn closed this as completed Jul 2, 2020
@Darksonn Darksonn removed E-easy Call for participation: Experience needed to fix: Easy / not much E-help-wanted Call for participation: Help is requested to fix this issue. labels Jul 2, 2020
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 C-maintenance Category: PRs that clean code up or issues documenting cleanup. M-sync Module: tokio/sync T-docs Topic: documentation
Projects
None yet
Development

No branches or pull requests

2 participants