about summary refs log tree commit diff
diff options
context:
space:
mode:
authorAndreas Molzer <andreas.molzer@gmx.de>2020-10-07 19:49:52 +0200
committerAndreas Molzer <andreas.molzer@gmx.de>2020-10-08 08:18:59 +0200
commitea206f2c5af8597771347ecc95e76c258b710181 (patch)
treede57d743bd78f590973f7a8655f1833aff04b4a8
parentdeec53052312ac709f6a37110b59ada486bea0bd (diff)
downloadrust-ea206f2c5af8597771347ecc95e76c258b710181.tar.gz
rust-ea206f2c5af8597771347ecc95e76c258b710181.zip
Add compile fail test for issue 27675
-rw-r--r--src/test/compile-fail/issue-27675-unchecked-bounds.rs19
1 files changed, 19 insertions, 0 deletions
diff --git a/src/test/compile-fail/issue-27675-unchecked-bounds.rs b/src/test/compile-fail/issue-27675-unchecked-bounds.rs
new file mode 100644
index 00000000000..1cfc2304531
--- /dev/null
+++ b/src/test/compile-fail/issue-27675-unchecked-bounds.rs
@@ -0,0 +1,19 @@
+/// The compiler previously did not properly check the bound of `From` when it was used from type
+/// of the dyn trait object (use in `copy_any` below). Since the associated type is under user
+/// control in this usage, the compiler could be tricked to believe any type implemented any trait.
+/// This would ICE, except for pure marker traits like `Copy`. It did not require providing an
+/// instance of the dyn trait type, only name said type.
+trait Setup {
+    type From: Copy;
+}
+
+fn copy<U: Setup + ?Sized>(from: &U::From) -> U::From {
+    *from
+}
+
+pub fn copy_any<T>(t: &T) -> T {
+    copy::<dyn Setup<From=T>>(t)
+    //~^ ERROR the trait bound `T: Copy` is not satisfied
+}
+
+fn main() {}