1 files changed, 0 insertions, 33 deletions
diff --git a/src/test/ui/pattern/bindings-after-at/nested-type-ascription-syntactically-invalid.rs b/src/test/ui/pattern/bindings-after-at/nested-type-ascription-syntactically-invalid.rs
deleted file mode 100644
index a709e34b5..000000000
--- a/src/test/ui/pattern/bindings-after-at/nested-type-ascription-syntactically-invalid.rs
+++ /dev/null
@@ -1,33 +0,0 @@
-// Here we check that type ascription is syntactically invalid when
-// not in the top position of an ascribing `let` binding or function parameter.
-
-
-// This has no effect.
-// We include it to demonstrate that this is the case:
-#![feature(type_ascription)]
-
-fn main() {}
-
-fn _ok() {
-    let _a @ _b: u8 = 0; // OK.
-    fn _f(_a @ _b: u8) {} // OK.
-}
-
-#[cfg(FALSE)]
-fn case_1() {
-    let a: u8 @ b = 0;
-    //~^ ERROR expected one of `!`
-}
-
-#[cfg(FALSE)]
-fn case_2() {
-    let a @ (b: u8);
-    //~^ ERROR expected one of `!`
-    //~| ERROR expected one of `)`
-}
-
-#[cfg(FALSE)]
-fn case_3() {
-    let a: T1 @ Outer(b: T2);
-    //~^ ERROR expected one of `!`
-}