- Notifications
You must be signed in to change notification settings - Fork341
Stabilize Future adapters and IntoFuture#884
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
2df9428
tof867373
CompareCI is failing because of#883 |
Btw, should we switch to libstd's IntoFuture or would that be breaking? |
@@ -47,8 +47,11 @@ | |||
//! [`Future::try_race`]: trait.Future.html#method.try_race | |||
cfg_alloc! { | |||
pub use into_future::IntoFuture; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
If you plan to replace this with re-export of std IntoFuture when std IntoFuture's is stable, that would be a breaking change. IIUC, theoretically, there is a way to avoid almost breakage. Seerust-lang/futures-rs#2207 andhttps://github.com/taiki-e/futures-compat-experiment for that.
@yoshuawuyts these CI failures look somewhat real to me |
Stabilizes several stream adapters that have been proven over the last year. Also stabilizes
IntoFuture
. Thanks!Changelog