rust/tests/ui/parser/match-refactor-to-expr.rs

//@ run-rustfix

fn main() {
    let foo =
        match //~ NOTE while parsing this `match` expression
        Some(4).unwrap_or(5)
        //~^ NOTE expected one of `.`, `?`, `{`, or an operator
        ; //~ NOTE unexpected token
        //~^ ERROR expected one of `.`, `?`, `{`, or an operator, found `;`

    println!("{}", foo)
}
[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives 2024-02-16 20:02:50 +00:00			`//@ run-rustfix`
Audit uses of `span_suggestion_short` 2020-07-02 14:32:12 +09:00
libsyntax: improve error message when a statement is prefixed with a match keyword 2015-10-27 13:41:55 +00:00			`fn main() {`
			`let foo =`
Tweak diagnostics * Recover from invalid `'label: ` before block. * Make suggestion to enclose statements in a block multipart. * Point at `match`, `while`, `loop` and `unsafe` keywords when failing to parse their expression. * Do not suggest `{ ; }`. * Do not suggest `\|` when very unlikely to be what was wanted (in `let` statements). 2022-01-12 20:43:24 +00:00			match //~ NOTE while parsing this `match` expression
Audit uses of `span_suggestion_short` 2020-07-02 14:32:12 +09:00			`Some(4).unwrap_or(5)`
Remove "here" from "expected one of X here" 2019-10-28 11:08:53 -07:00			//~^ NOTE expected one of `.`, `?`, `{`, or an operator
Point at last valid token on failed `expect_one_of` ```rust error: expected one of `.`, `;`, `?`, `}`, or an operator, found `)` --> $DIR/token-error-correct-3.rs:29:9 \| 25 \| foo() \| - expected one of `.`, `;`, `?`, `}`, or an operator after this ... 29 \| } else { \| ^ unexpected token ``` 2017-03-24 19:14:58 -07:00			`; //~ NOTE unexpected token`
			//~^ ERROR expected one of `.`, `?`, `{`, or an operator, found `;`
libsyntax: improve error message when a statement is prefixed with a match keyword 2015-10-27 13:41:55 +00:00
			`println!("{}", foo)`
			`}`