summaryrefslogtreecommitdiffstats
path: root/tests/ui/coherence/indirect-impl-for-trait-obj-coherence.rs
diff options
context:
space:
mode:
Diffstat (limited to 'tests/ui/coherence/indirect-impl-for-trait-obj-coherence.rs')
-rw-r--r--tests/ui/coherence/indirect-impl-for-trait-obj-coherence.rs25
1 files changed, 25 insertions, 0 deletions
diff --git a/tests/ui/coherence/indirect-impl-for-trait-obj-coherence.rs b/tests/ui/coherence/indirect-impl-for-trait-obj-coherence.rs
new file mode 100644
index 000000000..bb46498f9
--- /dev/null
+++ b/tests/ui/coherence/indirect-impl-for-trait-obj-coherence.rs
@@ -0,0 +1,25 @@
+// check-pass
+// known-bug: #57893
+
+// Should fail. Because we see an impl that uses a certain associated type, we
+// type-check assuming that impl is used. However, this conflicts with the
+// "implicit impl" that we get for trait objects, violating coherence.
+
+trait Object<U> {
+ type Output;
+}
+
+impl<T: ?Sized, U> Object<U> for T {
+ type Output = U;
+}
+
+fn foo<T: ?Sized, U>(x: <T as Object<U>>::Output) -> U {
+ x
+}
+
+#[allow(dead_code)]
+fn transmute<T, U>(x: T) -> U {
+ foo::<dyn Object<U, Output = T>, U>(x)
+}
+
+fn main() {}