-
Notifications
You must be signed in to change notification settings - Fork 679
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
chore: Apply Clippy lint redundant_clone
#5713
chore: Apply Clippy lint redundant_clone
#5713
Conversation
I think there are some issues in the test cache. |
Fixed CI build failures (due to code gated by cargo build --all-targets --all-features To be sure that there's no more hidden failures in code gated by feature flags |
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.
Wow, that's a lot of unnecessary clones! I'm curious if this will have any performance impact. I noticed one place that I think could be improved and will approve after the merge conflict is resolved and tests still pass.
Almost all of these are in test code, so node operators shouldn't really see any change, but we might notice Keep in mind manually optimizing test code has a much larger performance impact because it's built with |
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.
Approved assuming tests pass
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Description
Apply Clippy lint
redundant_clone
. Finds unnecessary calls to.clone()
,.to_string()
,.to_owned()
, etc. This is a nursery lint, and there are still a lot of false positives if you run it, but I think I got all the instances I could