-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Fix the emission order of trait_duplication_in_bounds
#9397
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
Conversation
* Emit the lint in source order * Make suggestions with multiple traits be in source order rather than alphabetical
r? @flip1995 (rust-highfive has picked a reviewer for you, use r? to override) |
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.
Change itself looks good to me. How does this issue cause the sync to fail?
| | ||
LL | fn bad_foo<T: Clone + Default, Z: Copy>(arg0: T, arg1: Z) | ||
| ^^^^^^^ | ||
| ^^^^^ |
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.
Both this and the next warning were both emitted with the order depending on the order of a hash map. I guess there was a change recently that caused the order be reversed.
Thanks for the fix! @bors r+ |
☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test |
Makes the lint emit in source order rather than whatever order the hash map happens to be in. This is currently blocking the sync into rustc.
changelog: None