-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
assigning_clones
should respect MSRV
#12511
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @Alexendoo (or someone else) some time within the next two weeks. Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (
|
Great, thanks! @bors r+ |
☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test |
Hi, thanks for the PR, but I'm pretty sure that |
Whoops! Sorry about that, I really should have double-checked exactly where to apply the MSRV check. I'll start working on a new PR to fix that, it looks like the proper location for the check would be in |
Make `assigning_clones` MSRV check more precise Continuation of #12511 `clone_into` is the only suggestion subject to the 1.63 MSRV requirement, and the lint should still emit other suggestions regardless of the MSRV. changelog: [assigning_clones]: only apply MSRV check to `clone_into` suggestions.
Fixes: #12502
This PR fixes the
assigning_clones
lint suggesting to useclone_from
orclone_into
on incompatible MSRVs.assigning_clones
will suggest using eitherclone_from
orclone_into
, both of which were stabilized in 1.63. If the current MSRV is below 1.63, the lint should not trigger.changelog: [
assigning_clones
]: don't lint when the MSRV is below 1.63.