-
Notifications
You must be signed in to change notification settings - Fork 1.7k
implicit_return
: better handling of asynchronous code
#14446
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
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
b4e7085
to
5e957c0
Compare
1fce8ce
to
2b85fc1
Compare
implicit_return
: do not suggest adding return
into desugared codeimplicit_return
: better handling of asynchronous code
The 23 new hits during Lintcheck all seem legitimate. The 5 changes lints are due to the fact that an enclosing HIR node now gets the lint. Rerunning Clippy after fixing this would reach the inner expressions. |
Also, be stricter in matching the right expansion of async closures.
Blocks created by desugaring will not contain an explicit `return`. Do not suggest to add it when the user has no control over the desugared code. Also, in the case of an implicit return on a `.await` expression, ensure that the suggested `return` is emitted at the right place instead of before the `await` keyword.
2b85fc1
to
4ac3611
Compare
Rebased |
r? clippy |
Alexendoo
approved these changes
Apr 11, 2025
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.
👍
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.
Blocks created by desugaring will not contain an explicit
return
. Do not suggest to add it when the user has no control over the desugared code.Also, ensure that in a
xxx.await
expression, the suggestedreturn
is emitted before the whole expression, not before theawait
keyword.Fix #14411
changelog: [
implicit_return
]: fix proposedreturn
position in the presence of asynchronous code