-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Fix suggestions for async
closures in redundant_closure_call
#9053
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
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @flip1995 (or someone else) soon. Please see the contribution instructions for more information. |
Just realised the suggestion is incorrect for single-expression blocks: Edit: Pushed a commit and new test for this case. The string interpolation feels a bit dirty here; if necessary, I'd be happy to have a shot at manipulating the AST properly, though I haven't done this with Rust's AST before! |
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.
Thanks! LGTM. Please squash your commits and this is ready to go.
Squashed! |
@bors r+ Thanks! |
☔ The latest upstream changes (presumably #9174) made this pull request unmergeable. Please resolve the merge conflicts. |
Fix redundant_closure_call for single-expression async closures Add Sugg::asyncify Use Sugg for redundant_closure_call implementation
What happened here? 🤔 Was bors on vacation? @bors r+ |
☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test |
Fixes #9052
changelog: Fix suggestions given by [
redundant_closure_call
] for async closures