rust/tests/ui/did_you_mean/trait-object-reference-without-parens-suggestion.stderr

error[E0178]: expected a path on the left-hand side of `+`, not `&Copy`
  --> $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 `+`, not `&'static Copy`
  --> $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` cannot be made into an object
  --> $DIR/trait-object-reference-without-parens-suggestion.rs:4:12
   |
LL |     let _: &Copy + 'static;
   |            ^^^^^ `Copy` cannot be made into an object
   |
   = note: the trait cannot be made into an object because it requires `Self: Sized`
   = note: for a trait to be "object safe" it needs to allow building a vtable to allow the call to be resolvable dynamically; for more information visit <https://doc.rust-lang.org/reference/items/traits.html#object-safety>

error: aborting due to 3 previous errors

Some errors have detailed explanations: E0038, E0178.
For more information about an error, try `rustc --explain E0038`.
Improve E0178 suggestion placement 2017-03-28 12:10:16 +00:00			error[E0178]: expected a path on the left-hand side of `+`, not `&Copy`
Update ui test suite to use dyn 2019-05-28 18:46:13 +00:00			`--> $DIR/trait-object-reference-without-parens-suggestion.rs:4:12`
Improve E0178 suggestion placement 2017-03-28 12:10:16 +00:00			`\|`
Update tests 2019-03-09 12:03:44 +00:00			`LL \| let _: &Copy + 'static;`
Make parse error suggestions verbose and fix spans Go over all structured parser suggestions and make them verbose style. When suggesting to add or remove delimiters, turn them into multiple suggestion parts. 2024-07-06 03:07:46 +00:00			`\| ^^^^^^^^^^^^^^^`
			`\|`
			`help: try adding parentheses`
			`\|`
			`LL \| let _: &(Copy + 'static);`
			`\| + +`
Improve E0178 suggestion placement 2017-03-28 12:10:16 +00:00
			error[E0178]: expected a path on the left-hand side of `+`, not `&'static Copy`
Update ui test suite to use dyn 2019-05-28 18:46:13 +00:00			`--> $DIR/trait-object-reference-without-parens-suggestion.rs:6:12`
Improve E0178 suggestion placement 2017-03-28 12:10:16 +00:00			`\|`
Update tests 2019-03-09 12:03:44 +00:00			`LL \| let _: &'static Copy + 'static;`
Make parse error suggestions verbose and fix spans Go over all structured parser suggestions and make them verbose style. When suggesting to add or remove delimiters, turn them into multiple suggestion parts. 2024-07-06 03:07:46 +00:00			`\| ^^^^^^^^^^^^^^^^^^^^^^^`
			`\|`
			`help: try adding parentheses`
			`\|`
			`LL \| let _: &'static (Copy + 'static);`
			`\| + +`
Improve E0178 suggestion placement 2017-03-28 12:10:16 +00:00
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not. 2020-09-02 07:40:56 +00:00			error[E0038]: the trait `Copy` cannot be made into an object
Update ui test suite to use dyn 2019-05-28 18:46:13 +00:00			`--> $DIR/trait-object-reference-without-parens-suggestion.rs:4:12`
Improve E0178 suggestion placement 2017-03-28 12:10:16 +00:00			`\|`
Update tests 2019-03-09 12:03:44 +00:00			`LL \| let _: &Copy + 'static;`
review comments 2020-10-20 00:57:18 +00:00			\| ^^^^^ `Copy` cannot be made into an object
Improve E0178 suggestion placement 2017-03-28 12:10:16 +00:00			`\|`
Wording changes to object unsafe trait errors Stemming from the thread at https://twitter.com/indygreg/status/1223279056398929920 2020-02-01 00:47:00 +00:00			= note: the trait cannot be made into an object because it requires `Self: Sized`
Tweak "object unsafe" errors Fix #77598. 2020-10-16 00:23:45 +00:00			`= note: for a trait to be "object safe" it needs to allow building a vtable to allow the call to be resolvable dynamically; for more information visit <https://doc.rust-lang.org/reference/items/traits.html#object-safety>`
Improve E0178 suggestion placement 2017-03-28 12:10:16 +00:00
report the total number of errors on compilation failure Prior to this PR, when we aborted because a "critical pass" failed, we displayed the number of errors from that critical pass. While that's the number of errors that caused compilation to abort in that place, that's not what people really want to know. Instead, always report the total number of errors, and don't bother to track the number of errors from the last pass that failed. This changes the compiler driver API to handle errors more smoothly, and therefore is a compiler-api-[breaking-change]. Fixes #42793. 2017-07-02 13:09:09 +00:00			`error: aborting due to 3 previous errors`
Improve E0178 suggestion placement 2017-03-28 12:10:16 +00:00
hide `--explain` hint if error has no extended info 2019-04-17 17:26:38 +00:00			`Some errors have detailed explanations: E0038, E0178.`
update tests 2018-03-03 14:59:40 +00:00			For more information about an error, try `rustc --explain E0038`.