rust/tests/ui/parser/trait-object-bad-parens.rs

#![feature(auto_traits)]
#![feature(negative_impls)]
#![allow(bare_trait_objects)]

auto trait Auto {}

fn main() {
    let _: Box<((Auto)) + Auto>; //~ ERROR expected a path on the left-hand side of `+`
    let _: Box<(Auto + Auto) + Auto>; //~ ERROR expected a path on the left-hand side of `+`
    let _: Box<(Auto +) + Auto>; //~ ERROR expected a path on the left-hand side of `+`
    let _: Box<(dyn Auto) + Auto>; //~ ERROR expected a path on the left-hand side of `+`
}
Rename `optin_builtin_traits` to `auto_traits` They were originally called "opt-in, built-in traits" (OIBITs), but people realized that the name was too confusing and a mouthful, and so they were renamed to just "auto traits". The feature flag's name wasn't updated, though, so that's what this PR does. There are some other spots in the compiler that still refer to OIBITs, but I don't think changing those now is worth it since they are internal and not particularly relevant to this PR. Also see <https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/opt-in.2C.20built-in.20traits.20(auto.20traits).20feature.20name>. 2020-11-22 19:54:31 -08:00			`#![feature(auto_traits)]`
introduce `negative_impls` feature gate and document They used to be covered by `optin_builtin_traits` but negative impls are now applicable to all traits, not just auto traits. This also adds docs in the unstable book for the current state of auto traits. 2020-01-09 05:56:38 -05:00			`#![feature(negative_impls)]`
Update test/ui/parser for bare_trait_object warnings 2019-05-28 14:45:27 -04:00			`#![allow(bare_trait_objects)]`
tests: Do not use `-Z parse-only`, continue compilation to test recovery 2019-01-06 18:33:05 +03:00
			`auto trait Auto {}`
syntax: Support parentheses around trait bounds 2017-04-05 01:12:53 +03:00
			`fn main() {`
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			let _: Box<((Auto)) + Auto>; //~ ERROR expected a path on the left-hand side of `+`
			let _: Box<(Auto + Auto) + Auto>; //~ ERROR expected a path on the left-hand side of `+`
			let _: Box<(Auto +) + Auto>; //~ ERROR expected a path on the left-hand side of `+`
			let _: Box<(dyn Auto) + Auto>; //~ ERROR expected a path on the left-hand side of `+`
syntax: Support parentheses around trait bounds 2017-04-05 01:12:53 +03:00			`}`