rust/src/test/ui/obsolete-in-place/bad.stderr

error: unexpected token: `<-`
  --> $DIR/bad.rs:5:7
   |
LL |     x <- y;
   |       ^^
   |
help: if you meant to write a comparison against a negative value, add a space in between `<` and `-`
   |
LL |     x < - y;
   |       ^^^

error: expected expression, found keyword `in`
  --> $DIR/bad.rs:10:5
   |
LL |     in(foo) { bar };
   |     ^^ expected expression

error: aborting due to 2 previous errors
Bring back suggestion for splitting `<-` into `< -` Closes #62632 2019-08-11 16:37:05 -05:00			error: unexpected token: `<-`
Update tests 2019-05-13 16:19:19 -05:00			`--> $DIR/bad.rs:5:7`
			`\|`
			`LL \| x <- y;`
Bring back suggestion for splitting `<-` into `< -` Closes #62632 2019-08-11 16:37:05 -05:00			`\| ^^`
Increase spacing for suggestions in diagnostics Make the spacing between the code snippet and verbose structured suggestions consistent with note and help messages. 2019-10-24 00:20:58 -05:00			`\|`
Bring back suggestion for splitting `<-` into `< -` Closes #62632 2019-08-11 16:37:05 -05:00			help: if you meant to write a comparison against a negative value, add a space in between `<` and `-`
			`\|`
			`LL \| x < - y;`
			`\| ^^^`
Update tests 2019-05-13 16:19:19 -05:00
			error: expected expression, found keyword `in`
Do not emit type errors after parse error in last statement of block When recovering from a parse error inside a block, do not emit type errors generating on that block's recovered return expression. Fix #57383. 2019-07-12 20:37:57 -05:00			`--> $DIR/bad.rs:10:5`
Update tests 2019-05-13 16:19:19 -05:00			`\|`
			`LL \| in(foo) { bar };`
			`\| ^^ expected expression`

Do not emit type errors after parse error in last statement of block When recovering from a parse error inside a block, do not emit type errors generating on that block's recovered return expression. Fix #57383. 2019-07-12 20:37:57 -05:00			`error: aborting due to 2 previous errors`
Update tests 2019-05-13 16:19:19 -05:00