Relax CallOnceFuture
/CallRefFuture
bound from Future
to IntoFuture
#127225
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 the change suggested in rust-lang/rfcs#3668 (comment). Blocked on some relevant team deciding whether to use
IntoFuture
orFuture
forAsyncFnOnce
bounds.This also adds
IntoFuture
andIntoFuture::Output
as lang items, so they can be referenced in those trait bounds.Notable: the concrete future returned by calling a concrete async closure still implements
Future
andIntoFuture
. This just makes the trait definition more generic, so the caller can pass more kinds of closures in.r? oli-obk
Tracking:
#![feature(async_closure)]
(RFC 2394 / RFC 3668) #62290