chore: Enable assigning_clones clippy lint#20670
Open
neilconway wants to merge 1 commit intoapache:mainfrom
Open
chore: Enable assigning_clones clippy lint#20670neilconway wants to merge 1 commit intoapache:mainfrom
assigning_clones clippy lint#20670neilconway wants to merge 1 commit intoapache:mainfrom
Conversation
alamb
approved these changes
Mar 4, 2026
Contributor
alamb
left a comment
There was a problem hiding this comment.
Seems reasonable to me -- thanks @neilconway
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
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.
Which issue does this PR close?
N/A
Rationale for this change
The
assigning_clonesclippy lint seems marginally useful. Enabling it for the whole workspace only catches a few places, but they are all coding patterns that could be improved.What changes are included in this PR?
assigning_clonesclippy lint as a workspace-level warningAre these changes tested?
Yes, covered by existing tests. This is a mechanical refactor that does not change behavior.
Are there any user-facing changes?
No.