rust/src/test/ui/parser/issue-15980.stderr

error: expected identifier, found keyword `return`
  --> $DIR/issue-15980.rs:10:13
   |
LL |         Err(ref e) if e.kind == io::EndOfFile {
   |                                 ------------- while parsing this struct
LL |             //~^ NOTE while parsing this struct
LL |             return
   |             ^^^^^^ expected identifier, found keyword
help: you can escape reserved keywords to use them as identifiers
   |
LL |             r#return
   |

error: expected one of `.`, `=>`, `?`, or an operator, found `_`
  --> $DIR/issue-15980.rs:15:9
   |
LL |         }
   |          - expected one of `.`, `=>`, `?`, or an operator here
LL |         //~^ NOTE expected one of `.`, `=>`, `?`, or an operator here
LL |         _ => {}
   |         ^ unexpected token

error: aborting due to 2 previous errors
`struct` pattern parsing and diagnostic tweaks - Recover from struct parse error on match and point out missing match body. - Point at struct when finding non-identifier while parsing its fields. - Add label to "expected identifier, found {}" error. 2018-01-06 16:43:20 -06:00			error: expected identifier, found keyword `return`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/issue-15980.rs:10:13`
`struct` pattern parsing and diagnostic tweaks - Recover from struct parse error on match and point out missing match body. - Point at struct when finding non-identifier while parsing its fields. - Add label to "expected identifier, found {}" error. 2018-01-06 16:43:20 -06:00			`\|`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| Err(ref e) if e.kind == io::EndOfFile {`
`struct` pattern parsing and diagnostic tweaks - Recover from struct parse error on match and point out missing match body. - Point at struct when finding non-identifier while parsing its fields. - Add label to "expected identifier, found {}" error. 2018-01-06 16:43:20 -06:00			`\| ------------- while parsing this struct`
Update UI tests 2018-02-24 17:01:39 -06:00			`LL \| //~^ NOTE while parsing this struct`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| return`
`struct` pattern parsing and diagnostic tweaks - Recover from struct parse error on match and point out missing match body. - Point at struct when finding non-identifier while parsing its fields. - Add label to "expected identifier, found {}" error. 2018-01-06 16:43:20 -06:00			`\| ^^^^^^ expected identifier, found keyword`
Address review comments - Suggest raw ident escaping in all editions - Keep primary label in all cases 2018-12-30 13:52:15 -06:00			`help: you can escape reserved keywords to use them as identifiers`
			`\|`
			`LL \| r#return`
			`\|`
`struct` pattern parsing and diagnostic tweaks - Recover from struct parse error on match and point out missing match body. - Point at struct when finding non-identifier while parsing its fields. - Add label to "expected identifier, found {}" error. 2018-01-06 16:43:20 -06:00
			error: expected one of `.`, `=>`, `?`, or an operator, found `_`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/issue-15980.rs:15:9`
`struct` pattern parsing and diagnostic tweaks - Recover from struct parse error on match and point out missing match body. - Point at struct when finding non-identifier while parsing its fields. - Add label to "expected identifier, found {}" error. 2018-01-06 16:43:20 -06:00			`\|`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| }`
`struct` pattern parsing and diagnostic tweaks - Recover from struct parse error on match and point out missing match body. - Point at struct when finding non-identifier while parsing its fields. - Add label to "expected identifier, found {}" error. 2018-01-06 16:43:20 -06:00			\| - expected one of `.`, `=>`, `?`, or an operator here
Update UI tests 2018-02-24 17:01:39 -06:00			LL \| //~^ NOTE expected one of `.`, `=>`, `?`, or an operator here
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| _ => {}`
`struct` pattern parsing and diagnostic tweaks - Recover from struct parse error on match and point out missing match body. - Point at struct when finding non-identifier while parsing its fields. - Add label to "expected identifier, found {}" error. 2018-01-06 16:43:20 -06:00			`\| ^ unexpected token`

Make sure all ui/parse tests have `-Z parse-only` Except those testing parsing during macro expansion 2018-10-20 16:38:23 -05:00			`error: aborting due to 2 previous errors`
`struct` pattern parsing and diagnostic tweaks - Recover from struct parse error on match and point out missing match body. - Point at struct when finding non-identifier while parsing its fields. - Add label to "expected identifier, found {}" error. 2018-01-06 16:43:20 -06:00