rust/tests/ui/coherence/coherence-impl-trait-for-marker-trait-positive.stderr

error[E0371]: the object type `(dyn Object + Marker2 + 'static)` automatically implements the trait `Marker1`
  --> $DIR/coherence-impl-trait-for-marker-trait-positive.rs:15:1
   |
LL | impl Marker1 for dyn Object + Marker2 { }
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `(dyn Object + Marker2 + 'static)` automatically implements trait `Marker1`

error[E0371]: the object type `(dyn Object + Marker2 + 'static)` automatically implements the trait `Marker2`
  --> $DIR/coherence-impl-trait-for-marker-trait-positive.rs:17:1
   |
LL | impl Marker2 for dyn Object + Marker2 { }
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `(dyn Object + Marker2 + 'static)` automatically implements trait `Marker2`

error[E0117]: only traits defined in the current crate can be implemented for arbitrary types
  --> $DIR/coherence-impl-trait-for-marker-trait-positive.rs:23:1
   |
LL | unsafe impl Send for dyn Marker2 {}
   | ^^^^^^^^^^^^^^^^^^^^^-----------
   | |                    |
   | |                    `dyn Marker2` 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[E0321]: cross-crate traits with a default impl, like `Send`, can only be implemented for a struct/enum type, not `(dyn Object + 'static)`
  --> $DIR/coherence-impl-trait-for-marker-trait-positive.rs:27:1
   |
LL | unsafe impl Send for dyn Object {}
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ can't implement cross-crate trait with a default impl for non-struct/enum type

error[E0321]: cross-crate traits with a default impl, like `Send`, can only be implemented for a struct/enum type, not `(dyn Object + Marker2 + 'static)`
  --> $DIR/coherence-impl-trait-for-marker-trait-positive.rs:28:1
   |
LL | unsafe impl Send for dyn Object + Marker2 {}
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ can't implement cross-crate trait with a default impl for non-struct/enum type

error: aborting due to 5 previous errors

Some errors have detailed explanations: E0117, E0321, E0371.
For more information about an error, try `rustc --explain E0117`.
Perform coherence checking per impl. 2021-05-09 13:53:13 -05:00			error[E0371]: the object type `(dyn Object + Marker2 + 'static)` automatically implements the trait `Marker1`
			`--> $DIR/coherence-impl-trait-for-marker-trait-positive.rs:15:1`
			`\|`
			`LL \| impl Marker1 for dyn Object + Marker2 { }`
			\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `(dyn Object + Marker2 + 'static)` automatically implements trait `Marker1`

			error[E0371]: the object type `(dyn Object + Marker2 + 'static)` automatically implements the trait `Marker2`
			`--> $DIR/coherence-impl-trait-for-marker-trait-positive.rs:17:1`
			`\|`
			`LL \| impl Marker2 for dyn Object + Marker2 { }`
			\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `(dyn Object + Marker2 + 'static)` automatically implements trait `Marker2`

forbid manually impl'ing one of an object type's marker traits This shouldn't break compatibility for crates that do not use `feature(optin_builtin_traits)`, because as the test shows, it is only possible to impl a marker trait for a trait object in the crate the marker trait is defined in, which must define `feature(optin_builtin_traits)`. Fixes #56934 2019-01-05 08:19:34 -06:00			`error[E0117]: only traits defined in the current crate can be implemented for arbitrary types`
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 04:56:38 -06:00			`--> $DIR/coherence-impl-trait-for-marker-trait-positive.rs:23:1`
forbid manually impl'ing one of an object type's marker traits This shouldn't break compatibility for crates that do not use `feature(optin_builtin_traits)`, because as the test shows, it is only possible to impl a marker trait for a trait object in the crate the marker trait is defined in, which must define `feature(optin_builtin_traits)`. Fixes #56934 2019-01-05 08:19:34 -06:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| unsafe impl Send for dyn Marker2 {}`
Use more targeted spans for orphan rule errors 2019-10-12 16:31:23 -05:00			`\| ^^^^^^^^^^^^^^^^^^^^^-----------`
			`\| \| \|`
Talk about specific types and remove lifetimes from output 2019-10-13 13:25:30 -05:00			\| \| `dyn Marker2` is not defined in the current crate
Use more targeted spans for orphan rule errors 2019-10-12 16:31:23 -05:00			`\| impl doesn't use only types from inside the current crate`
forbid manually impl'ing one of an object type's marker traits This shouldn't break compatibility for crates that do not use `feature(optin_builtin_traits)`, because as the test shows, it is only possible to impl a marker trait for a trait object in the crate the marker trait is defined in, which must define `feature(optin_builtin_traits)`. Fixes #56934 2019-01-05 08:19:34 -06:00			`\|`
			`= note: define and implement a trait or new type instead`

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 02:40:56 -05:00			error[E0321]: cross-crate traits with a default impl, like `Send`, can only be implemented for a struct/enum type, not `(dyn Object + 'static)`
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 04:56:38 -06:00			`--> $DIR/coherence-impl-trait-for-marker-trait-positive.rs:27:1`
forbid manually impl'ing one of an object type's marker traits This shouldn't break compatibility for crates that do not use `feature(optin_builtin_traits)`, because as the test shows, it is only possible to impl a marker trait for a trait object in the crate the marker trait is defined in, which must define `feature(optin_builtin_traits)`. Fixes #56934 2019-01-05 08:19:34 -06:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| unsafe impl Send for dyn Object {}`
forbid manually impl'ing one of an object type's marker traits This shouldn't break compatibility for crates that do not use `feature(optin_builtin_traits)`, because as the test shows, it is only possible to impl a marker trait for a trait object in the crate the marker trait is defined in, which must define `feature(optin_builtin_traits)`. Fixes #56934 2019-01-05 08:19:34 -06:00			`\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ can't implement cross-crate trait with a default impl for non-struct/enum type`

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 02:40:56 -05:00			error[E0321]: cross-crate traits with a default impl, like `Send`, can only be implemented for a struct/enum type, not `(dyn Object + Marker2 + 'static)`
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 04:56:38 -06:00			`--> $DIR/coherence-impl-trait-for-marker-trait-positive.rs:28:1`
forbid manually impl'ing one of an object type's marker traits This shouldn't break compatibility for crates that do not use `feature(optin_builtin_traits)`, because as the test shows, it is only possible to impl a marker trait for a trait object in the crate the marker trait is defined in, which must define `feature(optin_builtin_traits)`. Fixes #56934 2019-01-05 08:19:34 -06:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| unsafe impl Send for dyn Object + Marker2 {}`
forbid manually impl'ing one of an object type's marker traits This shouldn't break compatibility for crates that do not use `feature(optin_builtin_traits)`, because as the test shows, it is only possible to impl a marker trait for a trait object in the crate the marker trait is defined in, which must define `feature(optin_builtin_traits)`. Fixes #56934 2019-01-05 08:19:34 -06:00			`\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ can't implement cross-crate trait with a default impl for non-struct/enum type`

			`error: aborting due to 5 previous errors`

hide `--explain` hint if error has no extended info 2019-04-17 12:26:38 -05:00			`Some errors have detailed explanations: E0117, E0321, E0371.`
forbid manually impl'ing one of an object type's marker traits This shouldn't break compatibility for crates that do not use `feature(optin_builtin_traits)`, because as the test shows, it is only possible to impl a marker trait for a trait object in the crate the marker trait is defined in, which must define `feature(optin_builtin_traits)`. Fixes #56934 2019-01-05 08:19:34 -06:00			For more information about an error, try `rustc --explain E0117`.