-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
chore: apply Clippy suggestions and improve code formatting #10691
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
|
GNU testsuite comparison: |
|
GNU testsuite comparison: |
7489d4f to
adb143f
Compare
Merging this PR will not alter performance
Comparing Footnotes
|
|
GNU testsuite comparison: |
|
@nyurik I've been fixing some clippy lints, I usually stick to 1 lint per PR for ease of review |
|
GNU testsuite comparison: |
|
GNU testsuite comparison: |
f16d610 to
9f68c16
Compare
|
GNU testsuite comparison: |
|
GNU testsuite comparison: |
|
sorry but it conflicts |
|
sec, will fix in a min |
|
@sylvestre good to go? |
This comment was marked as resolved.
This comment was marked as resolved.
|
oops, missed it, thx, fixed |
|
i wish you were splitting it per class of linters |
|
GNU testsuite comparison: |
|
GNU testsuite comparison: |
I've split |
|
Thanks @xtqqczze , i removed it from this PR |
|
GNU testsuite comparison: |
|
GNU testsuite comparison: |
clippy::doc_link_with_quotesclippy::flat_map_optionclippy::format_push_stringclippy::from_iter_instead_of_collectclippy::large_types_passed_by_valueclippy::struct_field_namesclippy::unnested_or_patterns