summaryrefslogtreecommitdiffstats
path: root/src/test/ui/lub-glb/old-lub-glb-hr-eq.rs
diff options
context:
space:
mode:
Diffstat (limited to 'src/test/ui/lub-glb/old-lub-glb-hr-eq.rs')
-rw-r--r--src/test/ui/lub-glb/old-lub-glb-hr-eq.rs27
1 files changed, 0 insertions, 27 deletions
diff --git a/src/test/ui/lub-glb/old-lub-glb-hr-eq.rs b/src/test/ui/lub-glb/old-lub-glb-hr-eq.rs
deleted file mode 100644
index fbf4aee02..000000000
--- a/src/test/ui/lub-glb/old-lub-glb-hr-eq.rs
+++ /dev/null
@@ -1,27 +0,0 @@
-// Test that we give a note when the old LUB/GLB algorithm would have
-// succeeded but the new code (which requires equality) gives an
-// error. However, now that we handle subtyping correctly, we no
-// longer get an error, because we recognize these two types as
-// equivalent!
-//
-// check-pass
-
-fn foo(x: fn(&u8, &u8), y: for<'a> fn(&'a u8, &'a u8)) {
- // The two types above are actually equivalent. With the older
- // leak check, though, we didn't consider them as equivalent, and
- // hence we gave errors. But now we've fixed that.
- let z = match 22 {
- 0 => x,
- _ => y,
- };
-}
-
-fn foo_cast(x: fn(&u8, &u8), y: for<'a> fn(&'a u8, &'a u8)) {
- let z = match 22 {
- // No error with an explicit cast:
- 0 => x as for<'a> fn(&'a u8, &'a u8),
- _ => y,
- };
-}
-
-fn main() {}