rust/tests/ui/coherence/coherence-overlap-messages.rs

trait Foo { fn foo() {} }

impl<T> Foo for T {}
impl<U> Foo for U {}
//~^ ERROR E0119


trait Bar { fn bar() {} }

impl<T> Bar for (T, u8) {}
impl<T> Bar for (u8, T) {}
//~^ ERROR E0119

trait Baz<T> { fn baz() {} }

impl<T> Baz<u8> for T {}
impl<T> Baz<T> for u8 {}
//~^ ERROR E0119

trait Quux<U, V> { fn quux() {} }

impl<T, U, V> Quux<U, V> for T {}
impl<T, U> Quux<U, U> for T {}
//~^ ERROR E0119
impl<T, V> Quux<T, V> for T {}
//~^ ERROR E0119

fn main() {}
Implement RFC 1268 This patch allows overlap to occur between any two impls of a trait for traits which have no associated items. Several compile-fail tests around coherence had to be changed to add at least one item to the trait they test against. Ref #29864 2017-02-25 15:16:27 -06:00			`trait Foo { fn foo() {} }`
Provide overlapping types for coherence errors Currently, a coherence error based on overlapping impls simply mentions the trait, and points to the two conflicting impls: ``` error: conflicting implementations for trait `Foo` ``` With this commit, the error will include all input types to the trait (including the `Self` type) after unification between the overlapping impls. In other words, the error message will provide feedback with full type details, like: ``` error: conflicting implementations of trait `Foo<u32>` for type `u8`: ``` When the `Self` type for the two impls unify to an inference variable, it is elided in the output, since "for type `_`" is just noise in that case. Closes #23980 2015-12-01 13:26:47 -06:00
Adjust overlap-related tests to account for cosmetic changes to error reporting behavior 2015-12-29 23:18:24 -06:00			`impl<T> Foo for T {}`
Unify tests Implement compile tests as variants of existing tests 2018-12-28 17:11:13 -06:00			`impl<U> Foo for U {}`
Stabilize the `re_rebalance_coherence` feature 2019-10-26 10:28:02 -05:00			`//~^ ERROR E0119`
Unify tests Implement compile tests as variants of existing tests 2018-12-28 17:11:13 -06:00
Provide overlapping types for coherence errors Currently, a coherence error based on overlapping impls simply mentions the trait, and points to the two conflicting impls: ``` error: conflicting implementations for trait `Foo` ``` With this commit, the error will include all input types to the trait (including the `Self` type) after unification between the overlapping impls. In other words, the error message will provide feedback with full type details, like: ``` error: conflicting implementations of trait `Foo<u32>` for type `u8`: ``` When the `Self` type for the two impls unify to an inference variable, it is elided in the output, since "for type `_`" is just noise in that case. Closes #23980 2015-12-01 13:26:47 -06:00
Implement RFC 1268 This patch allows overlap to occur between any two impls of a trait for traits which have no associated items. Several compile-fail tests around coherence had to be changed to add at least one item to the trait they test against. Ref #29864 2017-02-25 15:16:27 -06:00			`trait Bar { fn bar() {} }`
Provide overlapping types for coherence errors Currently, a coherence error based on overlapping impls simply mentions the trait, and points to the two conflicting impls: ``` error: conflicting implementations for trait `Foo` ``` With this commit, the error will include all input types to the trait (including the `Self` type) after unification between the overlapping impls. In other words, the error message will provide feedback with full type details, like: ``` error: conflicting implementations of trait `Foo<u32>` for type `u8`: ``` When the `Self` type for the two impls unify to an inference variable, it is elided in the output, since "for type `_`" is just noise in that case. Closes #23980 2015-12-01 13:26:47 -06:00
Adjust overlap-related tests to account for cosmetic changes to error reporting behavior 2015-12-29 23:18:24 -06:00			`impl<T> Bar for (T, u8) {}`
Unify tests Implement compile tests as variants of existing tests 2018-12-28 17:11:13 -06:00			`impl<T> Bar for (u8, T) {}`
Stabilize the `re_rebalance_coherence` feature 2019-10-26 10:28:02 -05:00			`//~^ ERROR E0119`
Provide overlapping types for coherence errors Currently, a coherence error based on overlapping impls simply mentions the trait, and points to the two conflicting impls: ``` error: conflicting implementations for trait `Foo` ``` With this commit, the error will include all input types to the trait (including the `Self` type) after unification between the overlapping impls. In other words, the error message will provide feedback with full type details, like: ``` error: conflicting implementations of trait `Foo<u32>` for type `u8`: ``` When the `Self` type for the two impls unify to an inference variable, it is elided in the output, since "for type `_`" is just noise in that case. Closes #23980 2015-12-01 13:26:47 -06:00
Implement RFC 1268 This patch allows overlap to occur between any two impls of a trait for traits which have no associated items. Several compile-fail tests around coherence had to be changed to add at least one item to the trait they test against. Ref #29864 2017-02-25 15:16:27 -06:00			`trait Baz<T> { fn baz() {} }`
Provide overlapping types for coherence errors Currently, a coherence error based on overlapping impls simply mentions the trait, and points to the two conflicting impls: ``` error: conflicting implementations for trait `Foo` ``` With this commit, the error will include all input types to the trait (including the `Self` type) after unification between the overlapping impls. In other words, the error message will provide feedback with full type details, like: ``` error: conflicting implementations of trait `Foo<u32>` for type `u8`: ``` When the `Self` type for the two impls unify to an inference variable, it is elided in the output, since "for type `_`" is just noise in that case. Closes #23980 2015-12-01 13:26:47 -06:00
Adjust overlap-related tests to account for cosmetic changes to error reporting behavior 2015-12-29 23:18:24 -06:00			`impl<T> Baz<u8> for T {}`
Unify tests Implement compile tests as variants of existing tests 2018-12-28 17:11:13 -06:00			`impl<T> Baz<T> for u8 {}`
Stabilize the `re_rebalance_coherence` feature 2019-10-26 10:28:02 -05:00			`//~^ ERROR E0119`
Provide overlapping types for coherence errors Currently, a coherence error based on overlapping impls simply mentions the trait, and points to the two conflicting impls: ``` error: conflicting implementations for trait `Foo` ``` With this commit, the error will include all input types to the trait (including the `Self` type) after unification between the overlapping impls. In other words, the error message will provide feedback with full type details, like: ``` error: conflicting implementations of trait `Foo<u32>` for type `u8`: ``` When the `Self` type for the two impls unify to an inference variable, it is elided in the output, since "for type `_`" is just noise in that case. Closes #23980 2015-12-01 13:26:47 -06:00
Implement RFC 1268 This patch allows overlap to occur between any two impls of a trait for traits which have no associated items. Several compile-fail tests around coherence had to be changed to add at least one item to the trait they test against. Ref #29864 2017-02-25 15:16:27 -06:00			`trait Quux<U, V> { fn quux() {} }`
Provide overlapping types for coherence errors Currently, a coherence error based on overlapping impls simply mentions the trait, and points to the two conflicting impls: ``` error: conflicting implementations for trait `Foo` ``` With this commit, the error will include all input types to the trait (including the `Self` type) after unification between the overlapping impls. In other words, the error message will provide feedback with full type details, like: ``` error: conflicting implementations of trait `Foo<u32>` for type `u8`: ``` When the `Self` type for the two impls unify to an inference variable, it is elided in the output, since "for type `_`" is just noise in that case. Closes #23980 2015-12-01 13:26:47 -06:00
Adjust overlap-related tests to account for cosmetic changes to error reporting behavior 2015-12-29 23:18:24 -06:00			`impl<T, U, V> Quux<U, V> for T {}`
Unify tests Implement compile tests as variants of existing tests 2018-12-28 17:11:13 -06:00			`impl<T, U> Quux<U, U> for T {}`
Stabilize the `re_rebalance_coherence` feature 2019-10-26 10:28:02 -05:00			`//~^ ERROR E0119`
Unify tests Implement compile tests as variants of existing tests 2018-12-28 17:11:13 -06:00			`impl<T, V> Quux<T, V> for T {}`
Stabilize the `re_rebalance_coherence` feature 2019-10-26 10:28:02 -05:00			`//~^ ERROR E0119`
Provide overlapping types for coherence errors Currently, a coherence error based on overlapping impls simply mentions the trait, and points to the two conflicting impls: ``` error: conflicting implementations for trait `Foo` ``` With this commit, the error will include all input types to the trait (including the `Self` type) after unification between the overlapping impls. In other words, the error message will provide feedback with full type details, like: ``` error: conflicting implementations of trait `Foo<u32>` for type `u8`: ``` When the `Self` type for the two impls unify to an inference variable, it is elided in the output, since "for type `_`" is just noise in that case. Closes #23980 2015-12-01 13:26:47 -06:00
			`fn main() {}`