rust/tests/ui/coherence/coherence-fundamental-trait-objects.stderr

error[E0117]: only traits defined in the current crate can be implemented for arbitrary types
  --> $DIR/coherence-fundamental-trait-objects.rs:12:1
   |
LL | impl Misc for dyn Fundamental<Local> {}
   | ^^^^^^^^^^^^^^----------------------
   | |             |
   | |             `dyn Fundamental<Local>` is not defined in the current crate
   | impl doesn't use only types from inside the current crate
   |
   = note: define and implement a trait or new type instead

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0117`.
stop treating trait objects from #[fundamental] traits as fundamental Fixes #56503. 2018-12-15 21:45:37 +00:00			`error[E0117]: only traits defined in the current crate can be implemented for arbitrary types`
Stabilize the `re_rebalance_coherence` feature 2019-10-26 15:28:02 +00:00			`--> $DIR/coherence-fundamental-trait-objects.rs:12:1`
stop treating trait objects from #[fundamental] traits as fundamental Fixes #56503. 2018-12-15 21:45:37 +00:00			`\|`
			`LL \| impl Misc for dyn Fundamental<Local> {}`
Use more targeted spans for orphan rule errors 2019-10-12 21:31:23 +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			\| \| `dyn Fundamental<Local>` is not defined in the current crate
Use more targeted spans for orphan rule errors 2019-10-12 21:31:23 +00:00			`\| impl doesn't use only types from inside the current crate`
stop treating trait objects from #[fundamental] traits as fundamental Fixes #56503. 2018-12-15 21:45:37 +00:00			`\|`
			`= note: define and implement a trait or new type instead`

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`
stop treating trait objects from #[fundamental] traits as fundamental Fixes #56503. 2018-12-15 21:45:37 +00:00
			For more information about this error, try `rustc --explain E0117`.