rust/tests/ui/expr/if/attrs/let-chains-attr.rs

//@ check-pass
//@ edition:2024

#[cfg(false)]
fn foo() {
    #[attr]
    if let Some(_) = Some(true) && let Ok(_) = Ok(1) {
    } else if let Some(false) = Some(true) {
    }
}

fn main() {}
[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives 2024-02-16 20:02:50 +00:00			`//@ check-pass`
Remove let_chains feature gate from some places in the testsuite 2024-11-10 21:54:48 +01:00			`//@ edition:2024`
Revert let_chains stabilization This reverts commit 326646074940222d602f3683d0559088690830f4. This is the revert against master, the beta revert was already done in #100538. 2022-08-20 20:40:08 +02:00
Use `cfg(false)` in UI tests 2025-03-29 17:24:03 +00:00			`#[cfg(false)]`
Permit attributes on 'if' expressions Previously, attributes on 'if' expressions (e.g. #[attr] if true {}) were disallowed during parsing. This made it impossible for macros to perform any custom handling of such attributes (e.g. stripping them away), since a compilation error would be emitted before they ever had a chance to run. This PR permits attributes on 'if' expressions ('if-attrs' from here on). Both built-in attributes (e.g. `#[allow]`, `#[cfg]`) are supported. We still do not accept attributes on 'other parts' of an if-else chain. That is, the following code snippet still fails to parse: ```rust if true {} #[attr] else if false {} else #[attr] if false {} #[attr] else {} ``` 2020-02-15 19:04:20 -05:00			`fn foo() {`
			`#[attr]`
			`if let Some(_) = Some(true) && let Ok(_) = Ok(1) {`
			`} else if let Some(false) = Some(true) {`
			`}`
			`}`

			`fn main() {}`