For to_*
variant don't lint in trait impl taking self
when non-Copy
type
#7182
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.
Lint name:
wrong_self_convention
.It relaxes rules for
to_*
variant, so it doesn't lint in trait definitions and implementations anymore.Although, non-
Copy
type implementing trait'sto_*
method takingself
feels not good (consumes ownership, so should be rather namedinto_
), it would be better if this case was a pedantic lint (allow-by-default) instead.More information in the discussion with @flip1995 here
changelog:
wrong_self_convention
: Forto_*
variant don't lint in trait impl takingself
when non-Copy
typer? @flip1995