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 cancel-safety of StreamExt::next #2896

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

Conversation

akonradi-signal
Copy link

Fixes #2701

Copy link
Member

@taiki-e taiki-e left a comment

Choose a reason for hiding this comment

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

Thanks for the PR.

/// # Cancel safety
///
/// The returned future only holds a reference to the underlying stream, and
/// so is cancel safe (assuming the stream is also cancel-safe). If it is
Copy link
Member

Choose a reason for hiding this comment

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

assuming the stream is also cancel-safe

AFAIK, in the term "cancel-safe" used in tokio, cancel-safe is a property of Future and StreamExt::next is always cancel-safe. What is the definition of cancel-safe you are referring to?

https://docs.rs/tokio-stream/latest/tokio_stream/trait.StreamExt.html#method.next

Copy link
Author

@akonradi-signal akonradi-signal Feb 4, 2025

Choose a reason for hiding this comment

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

Good question. I'm drawing an analogy between Future::poll and Stream::poll_next, where calling the latter once but not until it returns Poll::Ready could lead to bad behavior.

The example I'm imagining is the result of calling StreamExt::chunks_timeout on a &mut impl Stream. Calling poll_once on that ChunksTimeout, then dropping it, then polling the wrapped stream could result in values from the input stream being dropped without ever being yielded. Given that possibility, I'd label ChunksTimeout not "cancel-safe".

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.

Document cancel safety of StreamExt::next
2 participants