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

fn main() { // we don't complain about the return type being `{integer}`
    let t = (42, 42);
    t.0::<isize>; //~ ERROR expected one of `.`, `;`, `?`, `}`, or an operator, found `::`
}

fn foo() -> usize { // we don't complain about the return type being unit
    let t = (42, 42);
    t.0::<isize>; //~ ERROR expected one of `.`, `;`, `?`, `}`, or an operator, found `::`
    42;
}
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			fn main() { // we don't complain about the return type being `{integer}`
Kill more `isize`s 2015-01-31 10:23:42 -06:00			`let t = (42, 42);`
update error messages in parse-fail tests 2016-03-07 20:17:31 -06:00			t.0::<isize>; //~ ERROR expected one of `.`, `;`, `?`, `}`, or an operator, found `::`
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			`}`

			`fn foo() -> usize { // we don't complain about the return type being unit`
			`let t = (42, 42);`
			t.0::<isize>; //~ ERROR expected one of `.`, `;`, `?`, `}`, or an operator, found `::`
			`42;`
Add test 2014-11-23 05:27:10 -06:00			`}`