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

Explain non-dropped sender recv in docs #80269

Merged
merged 1 commit into from
Jun 15, 2021
Merged

Commits on Jun 12, 2021

  1. Explain non-dropped sender recv in docs

    Original senders that are still hanging around could cause
    Receiver::recv to not block since this is a potential footgun
    for beginners, clarify more on this in the docs for readers to
    be aware about it.
    
    Fix minor tidbits in sender recv doc
    
    Co-authored-by: Dylan DPC <dylan.dpc@gmail.com>
    
    Add example for unbounded receive loops in doc
    
    Show the drop(tx) pattern, based on tokio docs
    https://tokio-rs.github.io/tokio/doc/tokio/sync/index.html
    
    Fix example code for drop sender recv
    
    Fix wording in sender docs
    
    Co-authored-by: Josh Triplett <josh@joshtriplett.org>
    pickfire and joshtriplett committed Jun 12, 2021
    Configuration menu
    Copy the full SHA
    0f3c7d1 View commit details
    Browse the repository at this point in the history