File: nested-type-ascription-syntactically-invalid.rs

package info (click to toggle)
rustc 1.85.0%2Bdfsg3-1
  • links: PTS, VCS
  • area: main
  • in suites: experimental, sid, trixie
  • size: 893,396 kB
  • sloc: xml: 158,127; python: 35,830; javascript: 19,497; cpp: 19,002; sh: 17,245; ansic: 13,127; asm: 4,376; makefile: 1,051; perl: 29; lisp: 29; ruby: 19; sql: 11
file content (32 lines) | stat: -rw-r--r-- 622 bytes parent folder | download | duplicates (5)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
// 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 `)`
}

#[cfg(FALSE)]
fn case_3() {
    let a: T1 @ Outer(b: T2);
    //~^ ERROR expected one of `!`
}