-
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
trivially_copy_pass_by_ref
fixes
#8639
trivially_copy_pass_by_ref
fixes
#8639
Conversation
r? @camsteffen (rust-highfive has picked a reviewer for you, use r? to override) |
☔ The latest upstream changes (presumably #8797) made this pull request unmergeable. Please resolve the merge conflicts. |
r? @dswij |
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.
Looks great, thanks for this!
There's some conflicts that needs to be resolved, and after that I think this is good to merge
5103fbe
to
c10101c
Compare
Thanks! @bors r+ |
📌 Commit c10101c has been approved by |
☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test |
fixes #5953
fixes #2961
The fix for #5953 is overly aggressive, but the suggestion is so bad that it's worth the false negatives. Basically three things together:
changelog: Don't lint
trivially_copy_pass_by_ref
when unsafe pointers are used.changelog: Better track lifetimes when linting
trivially_copy_pass_by_ref
.