-
-
Notifications
You must be signed in to change notification settings - Fork 14.6k
Improve irrefutable let-else lint wording #153048
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
Merged
rust-bors
merged 1 commit into
rust-lang:main
from
ozankenangungor:fix-irrefutable-let-else-wording
Mar 4, 2026
+128
−28
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,13 @@ | ||
| //@ check-pass | ||
|
|
||
| // Regression test for https://github.com/rust-lang/rust/issues/152938 | ||
| // The irrefutable `let...else` diagnostic should explain that the pattern | ||
| // always matches and point at the `else` block for removal. | ||
|
|
||
| pub fn say_hello(name: Option<String>) { | ||
| let name_str = Some(name) else { return; }; | ||
| //~^ WARN irrefutable `let...else` pattern | ||
| drop(name_str); | ||
| } | ||
|
|
||
| fn main() {} |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,16 @@ | ||
| warning: irrefutable `let...else` pattern | ||
| --> $DIR/let-else-irrefutable-152938.rs:8:5 | ||
| | | ||
| LL | let name_str = Some(name) else { return; }; | ||
| | ^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
| | | ||
| = note: this pattern always matches, so the else clause is unreachable | ||
| help: remove this `else` block | ||
| --> $DIR/let-else-irrefutable-152938.rs:8:36 | ||
| | | ||
| LL | let name_str = Some(name) else { return; }; | ||
| | ^^^^^^^^^^^ | ||
| = note: `#[warn(irrefutable_let_patterns)]` on by default | ||
|
|
||
| warning: 1 warning emitted | ||
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Can we turn this into a span_label pointing at the pattern (in most cases, a binding)? It might even make sense to detect when it is an identifier binding to explain in a note that all let bindings are patterns.
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.
Thanks, good idea. Right now the primary span already points at the pattern, and I tried to keep the wording generic to avoid extra logic. I would prefer to keep this pr small, I can follow up separately if we want to explore a span label binding specific note.