rust/tests/ui/resolve/tuple-struct-alias.rs

struct S(u8, u16);
type A = S;

fn main() {
    let s = A(0, 1); //~ ERROR expected function
    match s {
        A(..) => {} //~ ERROR expected tuple struct or tuple variant
    }
}
More systematic error reporting in path resolution 2016-12-01 01:35:25 +03:00			`struct S(u8, u16);`
			`type A = S;`

Add new error code tests 2016-08-04 01:51:52 +02:00			`fn main() {`
Merge cfail and ui tests into ui tests 2017-11-20 13:13:27 +01:00			`let s = A(0, 1); //~ ERROR expected function`
More systematic error reporting in path resolution 2016-12-01 01:35:25 +03:00			`match s {`
Point at local similarly named element and tweak references to variants Point at the span for the definition of ADTs internal to the current crate. Look at the leading char of the ident to determine whether we're expecting a likely fn or any of a fn, a tuple struct or a tuple variant. Turn fn `add_typo_suggestion` into a `Resolver` method. 2019-10-14 17:20:50 -07:00			`A(..) => {} //~ ERROR expected tuple struct or tuple variant`
More systematic error reporting in path resolution 2016-12-01 01:35:25 +03:00			`}`
Add new error code tests 2016-08-04 01:51:52 +02:00			`}`