-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
chore: clippy::redundant_closure_for_method_calls
#10704
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
base: main
Are you sure you want to change the base?
Conversation
CodSpeed Performance ReportMerging this PR will not alter performanceComparing Summary
Footnotes
|
e610f80 to
e9fc2d1
Compare
e9fc2d1 to
bec2f8e
Compare
|
thx @xtqqczze, makes sense, fixed |
|
GNU testsuite comparison: |
e3bac79 to
f81109c
Compare
redundant_closure_for_method_callsclippy::redundant_closure_for_method_calls
There's a lot of other cases we could use |
|
instead of to_string? I would generally agree, but this is not something we should spend too much time on - perhaps we can write a new clippy lint that uses some heuristic to determine which |
|
Good news: the |
Unfortunately, it doesn't trigger when the method is referenced directly, see rust-lang/rust-clippy#16511 |
|
@nyurik should we address |
|
@xtqqczze addressed in rust-lang/rust-clippy#16512 - I think this is a better way to catch everything :) |
f81109c to
6dafdbc
Compare
|
GNU testsuite comparison: |
@nyurik OK, since CI needs to run again anyway, let's revert the changes from 6dafdbc and then address them systematically in a new PR. |
Address `clippy::redundant_closure_for_method_calls`
6dafdbc to
0cc89d8
Compare
clippy::redundant_closure_for_method_calls