76adf05cfb
I was surprised to find that running with `-Zparse-only` only parses the crate root file. Other files aren't parsed because that happens later during expansion. This commit renames the option and updates the help message to make this clearer.
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 `+`, not `fn() -> A`
|
|
|
|
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 `+`, not `&A`
|
|
|
|
fn main() {}
|