rust/tests/ui/parser/issues/issue-24375.stderr

error: expected a pattern, found an expression
  --> $DIR/issue-24375.rs:6:9
   |
LL |         tmp[0] => {}
   |         ^^^^^^ not a pattern
   |
   = note: arbitrary expressions are not allowed in patterns: <https://doc.rust-lang.org/book/ch19-00-patterns.html>
help: consider moving the expression to a match arm guard
   |
LL -         tmp[0] => {}
LL +         val if val == tmp[0] => {}
   |
help: consider extracting the expression into a `const`
   |
LL +     const VAL: /* Type */ = tmp[0];
LL ~     match z {
LL ~         VAL => {}
   |

error: aborting due to 1 previous error
Handle methodcalls & operators in patterns 2024-01-28 16:12:21 +01:00			`error: expected a pattern, found an expression`
			`--> $DIR/issue-24375.rs:6:9`
Move parse-fail tests to UI 2018-10-20 23:36:17 +03:00			`\|`
Update tests 2019-03-09 15:03:44 +03:00			`LL \| tmp[0] => {}`
On function and method calls in patterns, link to the book ``` error: expected a pattern, found an expression --> f889.rs:3:13 \| 3 \| let (x, y.drop()) = (1, 2); //~ ERROR \| ^^^^^^^^ not a pattern \| = note: arbitrary expressions are not allowed in patterns: <https://doc.rust-lang.org/book/ch18-00-patterns.html> error[E0532]: expected a pattern, found a function call --> f889.rs:2:13 \| 2 \| let (x, drop(y)) = (1, 2); //~ ERROR \| ^^^^ not a tuple struct or tuple variant \| = note: function calls are not allowed in patterns: <https://doc.rust-lang.org/book/ch18-00-patterns.html> ``` Fix #97200. 2024-10-06 01:44:59 +00:00			`\| ^^^^^^ not a pattern`
Add suggestions for expressions in patterns 2024-09-18 20:38:43 +02:00			`\|`
Update tests for new TRPL chapter order 2024-10-30 13:08:08 -06:00			`= note: arbitrary expressions are not allowed in patterns: <https://doc.rust-lang.org/book/ch19-00-patterns.html>`
Add suggestions for expressions in patterns 2024-09-18 20:38:43 +02:00			`help: consider moving the expression to a match arm guard`
			`\|`
Show diff suggestion format on verbose replacement ``` error[E0610]: `{integer}` is a primitive type and therefore doesn't have fields --> $DIR/attempted-access-non-fatal.rs:7:15 \| LL \| let _ = 2.l; \| ^ \| help: if intended to be a floating point literal, consider adding a `0` after the period and a `f64` suffix \| LL - let _ = 2.l; LL + let _ = 2.0f64; \| ``` 2024-07-09 22:30:26 +00:00			`LL - tmp[0] => {}`
			`LL + val if val == tmp[0] => {}`
			`\|`
Add suggestions for expressions in patterns 2024-09-18 20:38:43 +02:00			help: consider extracting the expression into a `const`
			`\|`
			`LL + const VAL: /* Type */ = tmp[0];`
			`LL ~ match z {`
			`LL ~ VAL => {}`
			`\|`
Move parse-fail tests to UI 2018-10-20 23:36:17 +03:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
Move parse-fail tests to UI 2018-10-20 23:36:17 +03:00