rust/tests/ui/parser/intersection-patterns-1.stderr

error: pattern on wrong side of `@`
  --> $DIR/intersection-patterns-1.rs:17:9
   |
LL |         Some(x) @ y => {}
   |         -------^^^-
   |         |         |
   |         |         binding on the right, should be on the left
   |         pattern on the left, should be on the right
   |
help: switch the order
   |
LL -         Some(x) @ y => {}
LL +         y @ Some(x) => {}
   |

error: pattern on wrong side of `@`
  --> $DIR/intersection-patterns-1.rs:27:9
   |
LL |         1 ..= 5 @ e => {}
   |         -------^^^-
   |         |         |
   |         |         binding on the right, should be on the left
   |         pattern on the left, should be on the right
   |
help: switch the order
   |
LL -         1 ..= 5 @ e => {}
LL +         e @ 1..=5 => {}
   |

error: aborting due to 2 previous errors
syntax: add test for intersection pattern parser recovery 2019-10-14 14:57:18 +00:00			error: pattern on wrong side of `@`
Always suggest as `MachineApplicable` in `recover_intersection_pat` Signed-off-by: Yuki Okushi <jtitor@2k36.org> 2022-12-22 22:18:48 +00:00			`--> $DIR/intersection-patterns-1.rs:17:9`
syntax: add test for intersection pattern parser recovery 2019-10-14 14:57:18 +00:00			`\|`
			`LL \| Some(x) @ y => {}`
			`\| -------^^^-`
			`\| \| \|`
recover_intersection_pat: adjust wording 2019-10-14 16:02:49 +00:00			`\| \| binding on the right, should be on the left`
			`\| pattern on the left, should be on the right`
Make parse error suggestions verbose and fix spans Go over all structured parser suggestions and make them verbose style. When suggesting to add or remove delimiters, turn them into multiple suggestion parts. 2024-07-06 03:07:46 +00:00			`\|`
			`help: switch the order`
			`\|`
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 - Some(x) @ y => {}`
			`LL + y @ Some(x) => {}`
			`\|`
syntax: add test for intersection pattern parser recovery 2019-10-14 14:57:18 +00:00
			error: pattern on wrong side of `@`
Always suggest as `MachineApplicable` in `recover_intersection_pat` Signed-off-by: Yuki Okushi <jtitor@2k36.org> 2022-12-22 22:18:48 +00:00			`--> $DIR/intersection-patterns-1.rs:27:9`
syntax: add test for intersection pattern parser recovery 2019-10-14 14:57:18 +00:00			`\|`
			`LL \| 1 ..= 5 @ e => {}`
			`\| -------^^^-`
			`\| \| \|`
recover_intersection_pat: adjust wording 2019-10-14 16:02:49 +00:00			`\| \| binding on the right, should be on the left`
			`\| pattern on the left, should be on the right`
Make parse error suggestions verbose and fix spans Go over all structured parser suggestions and make them verbose style. When suggesting to add or remove delimiters, turn them into multiple suggestion parts. 2024-07-06 03:07:46 +00:00			`\|`
			`help: switch the order`
			`\|`
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 - 1 ..= 5 @ e => {}`
			`LL + e @ 1..=5 => {}`
			`\|`
syntax: add test for intersection pattern parser recovery 2019-10-14 14:57:18 +00:00
Always suggest as `MachineApplicable` in `recover_intersection_pat` Signed-off-by: Yuki Okushi <jtitor@2k36.org> 2022-12-22 22:18:48 +00:00			`error: aborting due to 2 previous errors`
syntax: add test for intersection pattern parser recovery 2019-10-14 14:57:18 +00:00