rust/tests/ui/parser/issues/issue-19096.stderr

error: expected one of `.`, `;`, `?`, `}`, or an operator, found `::`
  --> $DIR/issue-19096.rs:3:8
   |
LL |     t.0::<isize>;
   |        ^^ expected one of `.`, `;`, `?`, `}`, or an operator

error: expected one of `.`, `;`, `?`, `}`, or an operator, found `::`
  --> $DIR/issue-19096.rs:8:8
   |
LL |     t.0::<isize>;
   |        ^^ expected one of `.`, `;`, `?`, `}`, or an operator

error: aborting due to 2 previous errors
Move parse-fail tests to UI 2018-10-20 15:36:17 -05:00			error: expected one of `.`, `;`, `?`, `}`, or an operator, found `::`
tests: Do not use `-Z parse-only`, continue compilation to test recovery 2019-01-06 09:33:05 -06:00			`--> $DIR/issue-19096.rs:3:8`
Move parse-fail tests to UI 2018-10-20 15:36:17 -05:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| t.0::<isize>;`
Remove "here" from "expected one of X here" 2019-10-28 13:08:53 -05:00			\| ^^ expected one of `.`, `;`, `?`, `}`, or an operator
Move parse-fail tests to UI 2018-10-20 15:36:17 -05: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			error: expected one of `.`, `;`, `?`, `}`, or an operator, found `::`
			`--> $DIR/issue-19096.rs:8:8`
tests: Do not use `-Z parse-only`, continue compilation to test recovery 2019-01-06 09:33:05 -06:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| t.0::<isize>;`
Remove "here" from "expected one of X here" 2019-10-28 13:08:53 -05:00			\| ^^ expected one of `.`, `;`, `?`, `}`, or an operator
tests: Do not use `-Z parse-only`, continue compilation to test recovery 2019-01-06 09:33:05 -06:00
			`error: aborting due to 2 previous errors`
Move parse-fail tests to UI 2018-10-20 15:36:17 -05:00