6242335fdb
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`).
49 lines
1.3 KiB
Rust
49 lines
1.3 KiB
Rust
//@ compile-flags: -Z parse-crate-root-only
|
|
|
|
fn f() -> impl A + {} // OK
|
|
fn f() -> impl A + B {} // OK
|
|
fn f() -> dyn A + B {} // OK
|
|
fn f() -> A + B {} // OK
|
|
|
|
impl S {
|
|
fn f(self) -> impl A + { // OK
|
|
let _ = |a, b| -> impl A + {}; // OK
|
|
}
|
|
fn f(self) -> impl A + B { // OK
|
|
let _ = |a, b| -> impl A + B {}; // OK
|
|
}
|
|
fn f(self) -> dyn A + B { // OK
|
|
let _ = |a, b| -> dyn A + B {}; // OK
|
|
}
|
|
fn f(self) -> A + B { // OK
|
|
let _ = |a, b| -> A + B {}; // OK
|
|
}
|
|
}
|
|
|
|
type A = fn() -> impl A +;
|
|
//~^ ERROR ambiguous `+` in a type
|
|
type A = fn() -> impl A + B;
|
|
//~^ ERROR ambiguous `+` in a type
|
|
type A = fn() -> dyn A + B;
|
|
//~^ ERROR ambiguous `+` in a type
|
|
type A = fn() -> A + B;
|
|
//~^ ERROR expected a path on the left-hand side of `+`
|
|
|
|
type A = Fn() -> impl A +;
|
|
//~^ ERROR ambiguous `+` in a type
|
|
type A = Fn() -> impl A + B;
|
|
//~^ ERROR ambiguous `+` in a type
|
|
type A = Fn() -> dyn A + B;
|
|
//~^ ERROR ambiguous `+` in a type
|
|
type A = Fn() -> A + B; // OK, interpreted as `(Fn() -> A) + B` for compatibility
|
|
|
|
type A = &impl A +;
|
|
//~^ ERROR ambiguous `+` in a type
|
|
type A = &impl A + B;
|
|
//~^ ERROR ambiguous `+` in a type
|
|
type A = &dyn A + B;
|
|
//~^ ERROR ambiguous `+` in a type
|
|
type A = &A + B;
|
|
//~^ ERROR expected a path on the left-hand side of `+`
|
|
|
|
fn main() {}
|