Skip to content

Fix deadlock when all receivers are dropped #474

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

Merged
3 commits merged into from Nov 7, 2019
Merged

Fix deadlock when all receivers are dropped #474

3 commits merged into from Nov 7, 2019

Conversation

ghost
Copy link

@ghost ghost commented Nov 7, 2019

Closes #472

Copy link
Contributor

@yoshuawuyts yoshuawuyts left a comment

Choose a reason for hiding this comment

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

The code looks good to me, but I'm not sure I'm following how it's solved. Is the value sent, but dropped? It appears we're not panicking.

This seems like a great occasion to document what the behavior is.

@ghost
Copy link
Author

ghost commented Nov 7, 2019

I've disabled clippy for now and added a comment to the code. Hopefully it's a bit clearer now but we can revisit later if not.

@ghost ghost merged commit bc24503 into async-rs:master Nov 7, 2019
@ghost ghost deleted the fix-disconnection-bug branch November 7, 2019 22:01
This pull request was closed.
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.

Drop the channel receiver first, then the sender await forever
1 participant