-
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
Don't lint multiple_inherent_impl
with generic arguments
#7089
Conversation
r? @camsteffen (rust-highfive has picked a reviewer for you, use r? to override) |
84f8cac
to
23ddf7a
Compare
I don't think we should totally skip types with generic arguments. Instead we should detect if two impls have the exact same generic arguments. Since this is a restriction lint, some false positives are okay and even preferable to false negatives IMO. |
I'll keep this open while i look into it. |
637cabb
to
d962f37
Compare
That should do it. I'm not sure if that's the right way to add a dependency on |
d962f37
to
0bb198c
Compare
d6841da
to
d693380
Compare
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.
Looking good! Just need some comments as it's a little hard to parse.
57d488a
to
bd230fa
Compare
Please squash commits and r=me |
@bors delegate+ |
✌️ @Jarcho can now approve this pull request |
Treat different generic arguments as different types. Allow the lint to be ignored on the type definition, or any impl blocks.
bd230fa
to
760f703
Compare
@bors r+ |
📌 Commit 760f703 has been approved by |
☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test |
fixes: #5772
changelog: Treat different generic arguments as different types in
multiple_inherent_impl