
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`).
36 lines
1.2 KiB
Text
36 lines
1.2 KiB
Text
error[E0178]: expected a path on the left-hand side of `+`
|
|
--> $DIR/trait-object-reference-without-parens-suggestion.rs:4:12
|
|
|
|
|
LL | let _: &Copy + 'static;
|
|
| ^^^^^
|
|
|
|
|
help: try adding parentheses
|
|
|
|
|
LL | let _: &(Copy + 'static);
|
|
| + +
|
|
|
|
error[E0178]: expected a path on the left-hand side of `+`
|
|
--> $DIR/trait-object-reference-without-parens-suggestion.rs:6:12
|
|
|
|
|
LL | let _: &'static Copy + 'static;
|
|
| ^^^^^^^^^^^^^
|
|
|
|
|
help: try adding parentheses
|
|
|
|
|
LL | let _: &'static (Copy + 'static);
|
|
| + +
|
|
|
|
error[E0038]: the trait `Copy` is not dyn compatible
|
|
--> $DIR/trait-object-reference-without-parens-suggestion.rs:4:12
|
|
|
|
|
LL | let _: &Copy + 'static;
|
|
| ^^^^^ `Copy` is not dyn compatible
|
|
|
|
|
= note: the trait is not dyn compatible because it requires `Self: Sized`
|
|
= note: for a trait to be dyn compatible it needs to allow building a vtable
|
|
for more information, visit <https://doc.rust-lang.org/reference/items/traits.html#dyn-compatibility>
|
|
|
|
error: aborting due to 3 previous errors
|
|
|
|
Some errors have detailed explanations: E0038, E0178.
|
|
For more information about an error, try `rustc --explain E0038`.
|