add stream::FusedStream as "unstable" #326
Merged
Conversation
This file contains hidden or 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
Signed-off-by: Yoshua Wuyts <yoshuawuyts@gmail.com>
ghost
approved these changes
Oct 14, 2019
|
Ref #129 |
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.
Implements
Stream::FusedStream. This is a different API from futures-rs that instead is closer to std, and resembles the API futures-rs had prior to0.3.0-alpha.10(added in rust-lang/futures-rs#1259, October 2018).Because we don't require
select! {}for stream multiplexing in async-std, theis_terminatedmethod doesn't really serve a purpose for us, and really only requires extra bookkeeping.Because
FusedStreamis used for optimization purposes only, I think it's not a big deal to diverge from futures-rs on this account.Thanks!