rust-lang/rust
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity
Files
51b51b51d7931da85280382a81c4dd80c73ca754
rust/tests/ui/mir/issue-112269.stderr

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

36 lines
1.4 KiB
Plaintext
Raw Normal View History

Show note for type ascription interpreted as a constant pattern, not a new variable Given the code ```rust pub fn main() { const y: i32 = 4; let y: i32 = 3; } ``` `y` in the let binding is actually interpreted as a constant pattern and is not a new variable, causing confusing diagnostics about refutable patterns in local binding. This commit extends the note for type ascription as a constant pattern to `AscribeUserType` patterns as well.
2023-06-04 20:33:33 +08:00
error[E0005]: refutable pattern in local binding
--> $DIR/issue-112269.rs:3:9
|
Point at `const` definition when used instead of a binding in a `let` statement After: ``` error[E0005]: refutable pattern in local binding --> $DIR/bad-pattern.rs:19:13 | LL | const PAT: u32 = 0; | -------------- missing patterns are not covered because `PAT` is interpreted as a constant pattern, not a new variable ... LL | let PAT = v1; | ^^^ | | | pattern `1_u32..=u32::MAX` not covered | help: introduce a variable instead: `PAT_var` | = note: `let` bindings require an "irrefutable pattern", like a `struct` or an `enum` with only one variant = note: for more information, visit https://doc.rust-lang.org/book/ch18-02-refutability.html = note: the matched value is of type `u32` ``` Before: ``` error[E0005]: refutable pattern in local binding --> $DIR/bad-pattern.rs:19:13 | LL | let PAT = v1; | ^^^ | | | pattern `1_u32..=u32::MAX` not covered | missing patterns are not covered because `PAT` is interpreted as a constant pattern, not a new variable | help: introduce a variable instead: `PAT_var` | = note: `let` bindings require an "irrefutable pattern", like a `struct` or an `enum` with only one variant = note: for more information, visit https://doc.rust-lang.org/book/ch18-02-refutability.html = note: the matched value is of type `u32` ```
2024-11-06 19:46:54 +00:00
LL | const x: i32 = 4;
| ------------ missing patterns are not covered because `x` is interpreted as a constant pattern, not a new variable
Show note for type ascription interpreted as a constant pattern, not a new variable Given the code ```rust pub fn main() { const y: i32 = 4; let y: i32 = 3; } ``` `y` in the let binding is actually interpreted as a constant pattern and is not a new variable, causing confusing diagnostics about refutable patterns in local binding. This commit extends the note for type ascription as a constant pattern to `AscribeUserType` patterns as well.
2023-06-04 20:33:33 +08:00
LL | let x: i32 = 3;
Make suggestion verbose
2024-11-07 19:40:27 +00:00
| ^ patterns `i32::MIN..=3_i32` and `5_i32..=i32::MAX` not covered
Show note for type ascription interpreted as a constant pattern, not a new variable Given the code ```rust pub fn main() { const y: i32 = 4; let y: i32 = 3; } ``` `y` in the let binding is actually interpreted as a constant pattern and is not a new variable, causing confusing diagnostics about refutable patterns in local binding. This commit extends the note for type ascription as a constant pattern to `AscribeUserType` patterns as well.
2023-06-04 20:33:33 +08:00
|
= note: `let` bindings require an "irrefutable pattern", like a `struct` or an `enum` with only one variant
Update tests for new TRPL chapter order
2024-10-30 13:08:08 -06:00
= note: for more information, visit https://doc.rust-lang.org/book/ch19-02-refutability.html
Show note for type ascription interpreted as a constant pattern, not a new variable Given the code ```rust pub fn main() { const y: i32 = 4; let y: i32 = 3; } ``` `y` in the let binding is actually interpreted as a constant pattern and is not a new variable, causing confusing diagnostics about refutable patterns in local binding. This commit extends the note for type ascription as a constant pattern to `AscribeUserType` patterns as well.
2023-06-04 20:33:33 +08:00
= note: the matched value is of type `i32`
Make suggestion verbose
2024-11-07 19:40:27 +00:00
help: introduce a variable instead
|
Use underline suggestions for purely 'additive' replacements
2025-02-13 02:54:07 +00:00
LL | let x_var: i32 = 3;
Trim suggestion parts to the subset that is purely additive
2025-02-13 03:21:25 +00:00
| ++++
Show note for type ascription interpreted as a constant pattern, not a new variable Given the code ```rust pub fn main() { const y: i32 = 4; let y: i32 = 3; } ``` `y` in the let binding is actually interpreted as a constant pattern and is not a new variable, causing confusing diagnostics about refutable patterns in local binding. This commit extends the note for type ascription as a constant pattern to `AscribeUserType` patterns as well.
2023-06-04 20:33:33 +08:00
error[E0005]: refutable pattern in local binding
--> $DIR/issue-112269.rs:7:9
|
Point at `const` definition when used instead of a binding in a `let` statement After: ``` error[E0005]: refutable pattern in local binding --> $DIR/bad-pattern.rs:19:13 | LL | const PAT: u32 = 0; | -------------- missing patterns are not covered because `PAT` is interpreted as a constant pattern, not a new variable ... LL | let PAT = v1; | ^^^ | | | pattern `1_u32..=u32::MAX` not covered | help: introduce a variable instead: `PAT_var` | = note: `let` bindings require an "irrefutable pattern", like a `struct` or an `enum` with only one variant = note: for more information, visit https://doc.rust-lang.org/book/ch18-02-refutability.html = note: the matched value is of type `u32` ``` Before: ``` error[E0005]: refutable pattern in local binding --> $DIR/bad-pattern.rs:19:13 | LL | let PAT = v1; | ^^^ | | | pattern `1_u32..=u32::MAX` not covered | missing patterns are not covered because `PAT` is interpreted as a constant pattern, not a new variable | help: introduce a variable instead: `PAT_var` | = note: `let` bindings require an "irrefutable pattern", like a `struct` or an `enum` with only one variant = note: for more information, visit https://doc.rust-lang.org/book/ch18-02-refutability.html = note: the matched value is of type `u32` ```
2024-11-06 19:46:54 +00:00
LL | const y: i32 = 3;
| ------------ missing patterns are not covered because `y` is interpreted as a constant pattern, not a new variable
Show note for type ascription interpreted as a constant pattern, not a new variable Given the code ```rust pub fn main() { const y: i32 = 4; let y: i32 = 3; } ``` `y` in the let binding is actually interpreted as a constant pattern and is not a new variable, causing confusing diagnostics about refutable patterns in local binding. This commit extends the note for type ascription as a constant pattern to `AscribeUserType` patterns as well.
2023-06-04 20:33:33 +08:00
LL | let y = 4;
Make suggestion verbose
2024-11-07 19:40:27 +00:00
| ^ patterns `i32::MIN..=2_i32` and `4_i32..=i32::MAX` not covered
Show note for type ascription interpreted as a constant pattern, not a new variable Given the code ```rust pub fn main() { const y: i32 = 4; let y: i32 = 3; } ``` `y` in the let binding is actually interpreted as a constant pattern and is not a new variable, causing confusing diagnostics about refutable patterns in local binding. This commit extends the note for type ascription as a constant pattern to `AscribeUserType` patterns as well.
2023-06-04 20:33:33 +08:00
|
= note: `let` bindings require an "irrefutable pattern", like a `struct` or an `enum` with only one variant
Update tests for new TRPL chapter order
2024-10-30 13:08:08 -06:00
= note: for more information, visit https://doc.rust-lang.org/book/ch19-02-refutability.html
Show note for type ascription interpreted as a constant pattern, not a new variable Given the code ```rust pub fn main() { const y: i32 = 4; let y: i32 = 3; } ``` `y` in the let binding is actually interpreted as a constant pattern and is not a new variable, causing confusing diagnostics about refutable patterns in local binding. This commit extends the note for type ascription as a constant pattern to `AscribeUserType` patterns as well.
2023-06-04 20:33:33 +08:00
= note: the matched value is of type `i32`
Make suggestion verbose
2024-11-07 19:40:27 +00:00
help: introduce a variable instead
|
Use underline suggestions for purely 'additive' replacements
2025-02-13 02:54:07 +00:00
LL | let y_var = 4;
Trim suggestion parts to the subset that is purely additive
2025-02-13 03:21:25 +00:00
| ++++
Show note for type ascription interpreted as a constant pattern, not a new variable Given the code ```rust pub fn main() { const y: i32 = 4; let y: i32 = 3; } ``` `y` in the let binding is actually interpreted as a constant pattern and is not a new variable, causing confusing diagnostics about refutable patterns in local binding. This commit extends the note for type ascription as a constant pattern to `AscribeUserType` patterns as well.
2023-06-04 20:33:33 +08:00
error: aborting due to 2 previous errors
For more information about this error, try `rustc --explain E0005`.
Reference in New Issue Copy Permalink