-
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
Refactor unit types #6889
Refactor unit types #6889
Conversation
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.
This is especially a great refactor, since it combines 3 lint passes into 1. Only a NIT, that can be fixed in this PR, I think.
@bors delegate+ p=1 You can approve the PR yourself so it doesn't come to merge conflicts, once you've addressed my comment above. |
✌️ @Y-Nak can now approve this pull request |
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.
Those should be all the places this function is used.
☔ The latest upstream changes (presumably #6907) made this pull request unmergeable. Please resolve the merge conflicts. |
ecd25f7
to
2909b1c
Compare
Thanks for your review! |
📌 Commit 2909b1c has been approved by |
Refactor unit types Ref: #6724 r? `@flip1995` Changes: 1. Extract `unit_types` from `types` group. 2. Move lints of `unit_types` to their own modules. Notes: Other lints of `unit_types` is still scattered around the `clippy_lints`, e.g. `result_unit_err` or `option_map_unit_fn`. These should be addressed in another PR. changelog: none
@bors r- |
Oops! I thought |
☀️ Try build successful - checks-action_dev_test, checks-action_remark_test, checks-action_test |
@bors r=flip1995 |
📌 Commit 2909b1c has been approved by |
🔒 Merge conflict This pull request and the master branch diverged in a way that cannot be automatically merged. Please rebase on top of the latest master branch, and let the reviewer approve again. How do I rebase?Assuming
You may also read Git Rebasing to Resolve Conflicts by Drew Blessing for a short tutorial. Please avoid the "Resolve conflicts" button on GitHub. It uses Sometimes step 4 will complete without asking for resolution. This is usually due to difference between how Error message
|
☔ The latest upstream changes (presumably #6916) made this pull request unmergeable. Please resolve the merge conflicts. |
2909b1c
to
5a439f5
Compare
@bors r=flip1995 p=1 |
📌 Commit 5a439f5 has been approved by |
Refactor unit types Ref: #6724 r? `@flip1995` Changes: 1. Extract `unit_types` from `types` group. 2. Move lints of `unit_types` to their own modules. Notes: Other lints of `unit_types` is still scattered around the `clippy_lints`, e.g. `result_unit_err` or `option_map_unit_fn`. These should be addressed in another PR. changelog: none
💔 Test failed - checks-action_test |
@bors retry |
☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test |
Ref: #6724
r? @flip1995
Changes:
unit_types
fromtypes
group.unit_types
to their own modules.Notes:
Other lints of
unit_types
is still scattered around theclippy_lints
, e.g.result_unit_err
oroption_map_unit_fn
.These should be addressed in another PR.
changelog: none