rust/tests/ui/parser/trait-object-polytrait-priority.rs

#![allow(bare_trait_objects)]

trait Trait<'a> {}

fn main() {
    let _: &for<'a> Trait<'a> + 'static;
    //~^ ERROR expected a path on the left-hand side of `+`
    //~| HELP try adding parentheses
}
Update test/ui/parser for bare_trait_object warnings 2019-05-28 14:45:27 -04:00			`#![allow(bare_trait_objects)]`

Refactor parsing of trait object types 2017-03-17 00:47:32 +03:00			`trait Trait<'a> {}`

			`fn main() {`
			`let _: &for<'a> Trait<'a> + 'static;`
Improve diagnostic for E0178 (bad `+` in type) Namely, use a more sensical primary span. Don't pretty-print AST nodes for the diagnostic message. Why: * It's lossy (e.g., it doesn't replicate trailing `+`s in trait objects. * It's prone to leak error nodes (printed as `(/ERROR/)`) since the LHS can easily represent recovered code (e.g., `fn(i32?) + T`). 2025-04-15 07:44:24 +02:00			//~^ ERROR expected a path on the left-hand side of `+`
Refactor parsing of trait object types 2017-03-17 00:47:32 +03:00			`//~\| HELP try adding parentheses`
			`}`