-
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
Enable empty_loop lint for no_std crates #6205
Conversation
r? @phansch (rust_highfive has picked a reviewer for you, use r? to override) |
☔ The latest upstream changes (presumably #6109) made this pull request unmergeable. Please resolve the merge conflicts. Note that reviewers usually do not review pull requests until merge conflicts are resolved! Once you resolve the conflicts, you should change the labels applied by bors to indicate that your PR is ready for review. Post this as a comment to change the labels:
|
@rustbot modify labels: +S-waiting-on-author -S-waiting-on-review |
38087a8
to
c39386a
Compare
@flip1995 this is now rebased and ready for review. |
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.
Only NITs
@flip1995 NIT fixed, sorry for the delay, accidentally missed the email for this. |
We skip the lint if the `loop {}` is in the `#[panic_handler]` as the main recommendation we give is to panic, which obviously isn't possible in a panic handler. Signed-off-by: Joe Richey <[email protected]>
Fix NITs Co-authored-by: Philipp Krones <[email protected]>
@bors r+ Thanks! |
📌 Commit 00dee9d has been approved by |
☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test |
Depends on #6162. Fixes #6161
We skip the lint if the
loop {}
is in the#[panic_handler]
as themain recommendation we give is to panic, which obviously isn't
possible in a panic handler.
changelog: Enable empty_loop lint for no_std crates