make IntoFuture broadly usable #1102
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
With 1.64, IntoFuture is now stable. Therefore, most of our calls to .into_future() are no longer needed.
heaths
approved these changes
Sep 22, 2022
|
The current failures appear to be issues newly identified by clippy 1.64.0 unrelated to this PR. See #1103 for fixes. |
rylev
approved these changes
Sep 26, 2022
|
We pin the rust version in |
cataggar
approved these changes
Sep 26, 2022
|
@bmc-msft that only impacts people building directly from source. Users who take a dependency through crates.io or even GitHub will not be notified of this. |
cataggar
approved these changes
Sep 27, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
With 1.64, IntoFuture is now stable. Therefore, most of our calls to .into_future() are no longer needed.