rust/tests/ui/parser/issues/issue-101477-let.stderr

error: unexpected `==`
  --> $DIR/issue-101477-let.rs:4:11
   |
LL |     let x == 2;
   |           ^^
   |
help: try using `=` instead
   |
LL |     let x = 2;
   |           ~

error: aborting due to 1 previous error
fixes #101477: Recover from typo where == is used in place of = 2022-09-06 23:26:50 -05:00			error: unexpected `==`
			`--> $DIR/issue-101477-let.rs:4:11`
			`\|`
			`LL \| let x == 2;`
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-05 22:07:46 -05:00			`\| ^^`
			`\|`
			help: try using `=` instead
			`\|`
Fix ICE in suggestion caused by `⩵` being recovered as `==` The second suggestion shown here would previously incorrectly assume that the span corresponding to `⩵` was 2 bytes wide composed by 2 1 byte wide chars, so a span pointing at `==` could point only at one of the `=` to remove it. Instead, we now replace the whole thing (as we should have the whole time): ``` error: unknown start of token: \u{2a75} --> $DIR/unicode-double-equals-recovery.rs:1:16 \| LL \| const A: usize ⩵ 2; \| ^ \| help: Unicode character '⩵' (Two Consecutive Equals Signs) looks like '==' (Double Equals Sign), but it is not \| LL \| const A: usize == 2; \| ~~ error: unexpected `==` --> $DIR/unicode-double-equals-recovery.rs:1:16 \| LL \| const A: usize ⩵ 2; \| ^ \| help: try using `=` instead \| LL \| const A: usize = 2; \| ~ ``` 2024-07-16 17:43:30 -05:00			`LL \| let x = 2;`
			`\| ~`
fixes #101477: Recover from typo where == is used in place of = 2022-09-06 23:26:50 -05:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 09:44:16 -06:00			`error: aborting due to 1 previous error`
fixes #101477: Recover from typo where == is used in place of = 2022-09-06 23:26:50 -05:00