Refactor: prefer early returns in futures_util::future::select
#2587
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
Although a relatively small change, it makes the code a little bit more readable than the originally nested `match` expressions.
taiki-e
pushed a commit
that referenced
this pull request
Aug 14, 2022
Although a relatively small change, it makes the code a little bit more readable than the originally nested `match` expressions.
Merged
taiki-e
pushed a commit
that referenced
this pull request
Aug 14, 2022
Although a relatively small change, it makes the code a little bit more readable than the originally nested `match` expressions.
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.
Hello there! This PR slightly refactors the
future::selectimplementation so that it uses early returns. Although a relatively small change, I believe it makes the code a little bit more readable than the originally nestedmatchexpressions. It also makes the control flow clearer since it's more "linear", so to speak.In line with the readability improvements, I've also renamed the
xvariable tovalso that it's more apparent whatxrepresents.That is all. Thanks! 🎉