Allow calling UnboundedReceiver::try_next after None #2369
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Allow calling `UnboundedReceiver::try_next` and `Receiver::try_next`
after `None`: do not panic.
Not-panicking is equally safe, and does not have negative performance
implication.
It is irrelevant for `Stream` implementation to panic or not (because
`Stream` behavior is unspecified after `None`), but panicking in
`try_next` just complicates the interface: returned `Ok(None)` is
reasonable assumption to have.
Consider this use case: drain the queue on drop by performing
app-specific cleanup of queued messages.
The obvious implementation would be:
```
impl Drop for MyReceiverWrapper {
fn drop(&mut self) {
while let Ok(Some(m)) self.try_next() {
cleanup(m);
}
}
}
```
Without this change, I cannot even say for sure how this code need
to be implemented to avoid panicking. E. g. is `is_closed` enough
or some additional checks need to be performed?
taiki-e
reviewed
Mar 1, 2021
stepancheg
force-pushed
the
try-next-none-none
branch
from
45b2f80
to
2203386
Compare
|
Done. |
taiki-e
added
0.3-backport: pending
Merged
taiki-e
added
0.3-backport: completed
and removed
0.3-backport: pending
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Do not panic.
Not-panicking is equally safe, and does not have negative performance
implication.
It is irrelevant for
Streamimplementation to panic or not (becauseStreambehavior is unspecified afterNone), but panicking intry_nextjust complicates the interface: returnedOk(None)isreasonable assumption to have.
Consider this use case: drain the queue on drop by performing
app-specific cleanup of queued messages.
The obvious implementation would be:
Without this change, I cannot even say for sure how this code need
to be implemented to avoid panicking. E. g. is
is_closedenoughor some additional checks need to be performed?