Skip to content

Conversation

WaffleLapkin
Copy link
Member

@WaffleLapkin WaffleLapkin commented May 31, 2024

i.e. the #123590 change.

I can't seem to figure out how to make the lint work for panic!();, because the span of the statement does not include the ; (something weird going on in macro expansion)...

Other than that the lint is basically done.

Although this PR also requires changing std, so it doesn't error...

Tracking:

r? @compiler-errors

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels May 31, 2024
@compiler-errors
Copy link
Member

This PR shouldn't land anymore since we're no longer changing the diverging behavior, right?

@WaffleLapkin
Copy link
Member Author

At the very least not in the current form. I think a warning could be good, but not as a warn-by-default FCW.

@WaffleLapkin WaffleLapkin added S-blocked Status: Blocked on something else such as an RFC or other implementation work. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jul 7, 2024
@WaffleLapkin WaffleLapkin marked this pull request as draft July 7, 2024 14:39
@WaffleLapkin WaffleLapkin deleted the never_block_lint branch December 16, 2024 00:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-blocked Status: Blocked on something else such as an RFC or other implementation work. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants