-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Rename inconsistent_struct_constructor configuration; don't suggest deprecated configurations
#14280
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
0c3200f to
79e5125
Compare
y21
left a comment
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 good, thanks!
|
I can reproduce the failure locally. I will look into fixing it. EDIT: 🤞 EDIT 2: 😀 |
|
@y21 I just rebased this again. Do you think you could please try merging again? |
|
Sorry, my rebase left off one commit. Could you please try merging one more time? |
|
Thanks! |
|
Seems like this didn't make it into 1.86.0 release, but the changelog suggests the new name... |
The changelog uses the old name Line 45 in a5a033d
|
Sorry, my bad. I was looking at the clippy documentation (master), which mentioned this new name. No worries here. |
This PR does two things:
inconsistent_struct_constructor's configuration fromlint-inconsistent-struct-field-initializerstocheck-inconsistent-struct-field-initializers. (I should have suggestedcheck-...in #13737.)cyclomatic-complexity-threshold, for example.)r? @y21
changelog: Rename
lint-inconsistent-struct-field-initializerstocheck-inconsistent-struct-field-initializerschangelog: No longer suggest deprecated configurations