regression: parsing change in allow()?

[Mark-Simulacrum]

https://crater-reports.s3.amazonaws.com/beta-1.74-4/beta-2023-10-21/gh/ken-matsui.diagonal-loop/log.txt

[INFO] [stdout] error: expected one of `(`, `,`, `::`, or `=`, found `-`
[INFO] [stdout]   --> src/dim2.rs:28:36
[INFO] [stdout]    |
[INFO] [stdout] 28 |         #[allow(clippy::collapsible-else-if)]
[INFO] [stdout]    |                                    ^ expected one of `(`, `,`, `::`, or `=`

[Nilstrieb]

searched nightlies: from nightly-2023-08-01 to nightly-2023-10-10
regressed nightly: nightly-2023-09-15
searched commit range: 8142a31...ca2b74f
regressed commit: dac91a8

bisected with cargo-bisect-rustc v0.6.6

Host triple: x86_64-unknown-linux-gnu
Reproduce with:

cargo bisect-rustc 2023-08-01 --end 2023-10-10 --access github --regress error 

this bisection may look pretty nonsensical, but I did manually confirm that nightly-2023-09-14 worked and nightly-2023-09-16 didn't. I am surprised that this ever parsed, and given that there's only a single random repo that regressed, and the regressing code is a mistake, I don't think this is a problematic regression. @matthewjasper anyways.

[Mark-Simulacrum]

Agreed that we don't necessarily need a fix, but we should try to make sure that this is indeed limited to this one case (i.e., it's not some broader incompatibility that may have gone uncaught in Crater)

[matthewjasper]

The change here is that AST validation is now checking that the attribute is valid. Some other cases:

fn allow_if() {
    #[allow(two-words)]
    if true {} else {}
    #[allow(two-words)]
    (1);
    #[allow(two-words)]
    match 1 { _ => {} }
    #[allow(two-words)]
    while false {}
}

Marking as needs-test, with the new behavior being correct