rust/src/test/ui/parser/raw/raw-literal-keywords.stderr

error: expected one of `!`, `.`, `::`, `;`, `?`, `{`, `}`, or an operator, found keyword `true`
  --> $DIR/raw-literal-keywords.rs:2:10
   |
LL |     r#if true { }
   |          ^^^^ expected one of 8 possible tokens here

error: expected one of `!`, `.`, `::`, `;`, `?`, `{`, `}`, or an operator, found `Test`
  --> $DIR/raw-literal-keywords.rs:6:14
   |
LL |     r#struct Test;
   |              ^^^^ expected one of 8 possible tokens here

error: expected one of `!`, `.`, `::`, `;`, `?`, `{`, `}`, or an operator, found `Test`
  --> $DIR/raw-literal-keywords.rs:10:13
   |
LL |     r#union Test;
   |             ^^^^ expected one of 8 possible tokens here

error[E0425]: cannot find value `if` in this scope
  --> $DIR/raw-literal-keywords.rs:14:13
   |
LL |     let _ = r#if;
   |             ^^^^ not found in this scope

error[E0425]: cannot find value `struct` in this scope
  --> $DIR/raw-literal-keywords.rs:18:13
   |
LL |     let _ = r#struct;
   |             ^^^^^^^^ not found in this scope

error[E0425]: cannot find value `union` in this scope
  --> $DIR/raw-literal-keywords.rs:22:13
   |
LL |     let _ = r#union;
   |             ^^^^^^^ not found in this scope

error: aborting due to 6 previous errors

For more information about this error, try `rustc --explain E0425`.
Tweak unexpected token wording 2019-10-22 13:46:19 -05:00			error: expected one of `!`, `.`, `::`, `;`, `?`, `{`, `}`, or an operator, found keyword `true`
tests: Do not use `-Z parse-only`, continue compilation to test recovery 2019-01-06 09:33:05 -06:00			`--> $DIR/raw-literal-keywords.rs:2:10`
Initial implementation of RFC 2151, Raw Identifiers 2018-03-09 23:56:40 -06:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| r#if true { }`
Initial implementation of RFC 2151, Raw Identifiers 2018-03-09 23:56:40 -06:00			`\| ^^^^ expected one of 8 possible tokens here`

			error: expected one of `!`, `.`, `::`, `;`, `?`, `{`, `}`, or an operator, found `Test`
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/raw-literal-keywords.rs:6:14`
Initial implementation of RFC 2151, Raw Identifiers 2018-03-09 23:56:40 -06:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| r#struct Test;`
Initial implementation of RFC 2151, Raw Identifiers 2018-03-09 23:56:40 -06:00			`\| ^^^^ expected one of 8 possible tokens here`

			error: expected one of `!`, `.`, `::`, `;`, `?`, `{`, `}`, or an operator, found `Test`
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/raw-literal-keywords.rs:10:13`
Initial implementation of RFC 2151, Raw Identifiers 2018-03-09 23:56:40 -06:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| r#union Test;`
Initial implementation of RFC 2151, Raw Identifiers 2018-03-09 23:56:40 -06:00			`\| ^^^^ expected one of 8 possible tokens here`

tests: Do not use `-Z parse-only`, continue compilation to test recovery 2019-01-06 09:33:05 -06:00			error[E0425]: cannot find value `if` in this scope
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/raw-literal-keywords.rs:14:13`
tests: Do not use `-Z parse-only`, continue compilation to test recovery 2019-01-06 09:33:05 -06:00			`\|`
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			`LL \| let _ = r#if;`
			`\| ^^^^ not found in this scope`
tests: Do not use `-Z parse-only`, continue compilation to test recovery 2019-01-06 09:33:05 -06:00
			error[E0425]: cannot find value `struct` in this scope
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/raw-literal-keywords.rs:18:13`
tests: Do not use `-Z parse-only`, continue compilation to test recovery 2019-01-06 09:33:05 -06:00			`\|`
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			`LL \| let _ = r#struct;`
			`\| ^^^^^^^^ not found in this scope`
tests: Do not use `-Z parse-only`, continue compilation to test recovery 2019-01-06 09:33:05 -06:00
			error[E0425]: cannot find value `union` in this scope
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/raw-literal-keywords.rs:22:13`
tests: Do not use `-Z parse-only`, continue compilation to test recovery 2019-01-06 09:33:05 -06:00			`\|`
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			`LL \| let _ = r#union;`
			`\| ^^^^^^^ not found in this scope`
tests: Do not use `-Z parse-only`, continue compilation to test recovery 2019-01-06 09:33:05 -06:00
			`error: aborting due to 6 previous errors`
Initial implementation of RFC 2151, Raw Identifiers 2018-03-09 23:56:40 -06:00
tests: Do not use `-Z parse-only`, continue compilation to test recovery 2019-01-06 09:33:05 -06:00			For more information about this error, try `rustc --explain E0425`.