1 files changed, 0 insertions, 30 deletions
diff --git a/src/test/ui/or-patterns/or-patterns-syntactic-fail.rs b/src/test/ui/or-patterns/or-patterns-syntactic-fail.rs
deleted file mode 100644
index 358e9d034c4..00000000000
--- a/src/test/ui/or-patterns/or-patterns-syntactic-fail.rs
+++ /dev/null
@@ -1,30 +0,0 @@
-// Test some cases where or-patterns may ostensibly be allowed but are in fact not.
-// This is not a semantic test. We only test parsing.
-
-fn main() {}
-
-enum E { A, B }
-use E::*;
-
-fn no_top_level_or_patterns() {
-    // We do *not* allow or-patterns at the top level of lambdas...
-    let _ = |A | B: E| (); //~ ERROR no implementation for `E | ()`
-    //           -------- This looks like an or-pattern but is in fact `|A| (B: E | ())`.
-
-    // ...and for now neither do we allow or-patterns at the top level of functions.
-    fn fun1(A | B: E) {}
-    //~^ ERROR top-level or-patterns are not allowed
-
-    fn fun2(| A | B: E) {}
-    //~^ ERROR top-level or-patterns are not allowed
-
-    // We don't allow top-level or-patterns before type annotation in let-statements because we
-    // want to reserve this syntactic space for possible future type ascription.
-    let A | B: E = A;
-    //~^ ERROR top-level or-patterns are not allowed
-
-    let | A | B: E = A;
-    //~^ ERROR top-level or-patterns are not allowed
-
-    let (A | B): E = A; // ok -- wrapped in parens
-}