Type specifiers with generic args in certain positions should generate errors that reference the turbofish

[aathan]

Code

I'm having trouble creating a concise example, but perhaps the error below is enough. If the error at least mentioned turbofish it'd have saved a bunch of heartache for a noob.

Current output

error: expected one of `)`, `,`, `@`, or `|`, found `<`
   --> ....
    |
143 |             Ok(SomeEnum<STRICT>::SomeVariant { result, .. }) => { ... },
    |                           ^
    |                           |
    |                           expected one of `)`, `,`, `@`, or `|`
    |                           help: missing `,`

Desired output

" if SomeEnum<STRICT> is a type reference, use SomeEnum::<STRICT> instead"

Rationale and extra context

Rust is elsewhere good about suggesting the turbofish.

Other cases

No response

Anything else?

No response

[mu001999]

An example (play):

enum E<T> {
    A(T)
}

fn main() {
    match E::A(1) {
        E<i32>::A(v) => {
            println!("{v:?}");
        },
    }
}

[estebank]

To summarize, the parser needs to keep into account a lack of turbofish in patterns. It already does in expressions, and the same strategy can likely be used.

[mu001999]

@rustbot claim