rust/tests/ui/issues/issue-56806.stderr

error[E0307]: invalid `self` parameter type: Box<(dyn Trait + 'static)>
  --> $DIR/issue-56806.rs:2:34
   |
LL |     fn dyn_instead_of_self(self: Box<dyn Trait>);
   |                                  ^^^^^^^^^^^^^^
   |
   = note: type of `self` must be `Self` or a type that dereferences to it
   = help: consider changing to `self`, `&self`, `&mut self`, `self: Box<Self>`, `self: Rc<Self>`, `self: Arc<Self>`, or `self: Pin<P>` (where P is one of the previous types except `Self`)

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0307`.
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[E0307]: invalid `self` parameter type: Box<(dyn Trait + 'static)>
use `delay_span_bug` instead of `bug!` when doing layout sanity check It's possible that `is_object_safe` is called on a trait that is ill-formed, and we shouldn't ICE unless there are no errors being raised. Using `delay_span_bug` solves this. fixes #56806 2018-12-19 23:27:58 +00:00			`--> $DIR/issue-56806.rs:2:34`
			`\|`
			`LL \| fn dyn_instead_of_self(self: Box<dyn Trait>);`
			`\| ^^^^^^^^^^^^^^`
			`\|`
Refer to "`self` type" instead of "receiver type" 2019-09-03 01:21:58 +00:00			= note: type of `self` must be `Self` or a type that dereferences to it
Update the help message on error for self type 2019-07-16 04:30:48 +00:00			= help: consider changing to `self`, `&self`, `&mut self`, `self: Box<Self>`, `self: Rc<Self>`, `self: Arc<Self>`, or `self: Pin<P>` (where P is one of the previous types except `Self`)
use `delay_span_bug` instead of `bug!` when doing layout sanity check It's possible that `is_object_safe` is called on a trait that is ill-formed, and we shouldn't ICE unless there are no errors being raised. Using `delay_span_bug` solves this. fixes #56806 2018-12-19 23:27:58 +00:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
use `delay_span_bug` instead of `bug!` when doing layout sanity check It's possible that `is_object_safe` is called on a trait that is ill-formed, and we shouldn't ICE unless there are no errors being raised. Using `delay_span_bug` solves this. fixes #56806 2018-12-19 23:27:58 +00:00
Refer to "`self` type" instead of "receiver type" 2019-09-03 01:21:58 +00:00			For more information about this error, try `rustc --explain E0307`.