-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
Fix pattern_from_macro_note for bit-or expr
#154369
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
Open
ver-nyan
wants to merge
1
commit into
rust-lang:main
Choose a base branch
from
ver-nyan:fix-bit_or-pat_macro-msg
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+26
−3
Open
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 |
|---|---|---|
| @@ -1,10 +1,18 @@ | ||
| error: arbitrary expressions aren't allowed in patterns | ||
| --> $DIR/expr-in-pat-issue-99380.rs:10:10 | ||
| --> $DIR/expr-in-pat-issue-99380.rs:19:10 | ||
| | | ||
| LL | foo!(Some(3)); | ||
| | ^^^^^^^ | ||
| | | ||
| = note: the `expr` fragment specifier forces the metavariable's content to be an expression | ||
|
|
||
| error: aborting due to 1 previous error | ||
| error: arbitrary expressions aren't allowed in patterns | ||
| --> $DIR/expr-in-pat-issue-99380.rs:21:33 | ||
| | | ||
| LL | let _ = custom_matches!(67, 6 | 7); | ||
| | ^^^^^ | ||
| | | ||
| = note: the `expr` fragment specifier forces the metavariable's content to be an expression | ||
|
|
||
| error: aborting due to 2 previous errors | ||
|
|
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
I'm curious, is there a specific reason why you didn't move this check into
is_approximately_pattern? Did it negatively impact other diagnostics that use this method?Edit: Moving it into that function would also allow you to recurse into the operands to ensure that they're approximately patterns, too.
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.
I initially had it isolated in
lower_expr_within_pat()bc it ended up doing an incorrectsuggest_pattern_match_with_let()e.g.
Recursively
lhs.is_approximately_pattern() || rhs.is_approximately_pattern()unfortunately didn't work since it would end up matchingExprKind::Lit(_)down the line.Uh oh!
There was an error while loading. Please reload this page.
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.
I just learned that undeclared variables are
ExprKind::Path, so bothLitandPathwill cause false positiveletsuggestion :cA more formal example extending
tests/ui/expr/if/bad-if-let-suggestion.rs:Edit: also i think a recursive approach would lose it's "first-order'ness"
rust/compiler/rustc_ast/src/ast.rs
Lines 1638 to 1639 in 64d5cb6