regression: no rules expected the token `.`

[Mark-Simulacrum]

https://crater-reports.s3.amazonaws.com/beta-1.77-3/beta-2024-02-18/reg/gen-nested-iter-yield-0.1.3/log.txt

[INFO] [stdout] error: no rules expected the token `.`
[INFO] [stdout]   --> tests/tests.rs:45:13
[INFO] [stdout]    |
[INFO] [stdout] 45 |             nested_iter_yield!(input_vector.iter(), 2, .clone())
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ no rules expected this token in macro call
[INFO] [stdout]    |
[INFO] [stdout]    = note: while trying to match end of macro
[INFO] [stdout]    = note: this error originates in the macro `nested_iter_yield` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: no rules expected the token `.`
[INFO] [stdout]   --> tests/tests.rs:67:13
[INFO] [stdout]    |
[INFO] [stdout] 67 |             nested_iter_yield!(input_vector.iter(), 2, .clone(), ::)
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ no rules expected this token in macro call
[INFO] [stdout]    |
[INFO] [stdout]    = note: while trying to match end of macro
[INFO] [stdout]    = note: this error originates in the macro `nested_iter_yield` (in Nightly builds, run with -Z macro-backtrace for more info)

[compiler-errors]

More regressions from macro spacing -- #120227

cc @nnethercote @petrochenkov

---

searched nightlies: from nightly-2024-01-01 to nightly-2024-02-26
regressed nightly: nightly-2024-02-01
searched commit range: cb4d9a1...11f32b7
regressed commit: 80deabd

bisected with cargo-bisect-rustc v0.6.7

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

cargo bisect-rustc --start=2024-01-01 -- test

[nnethercote]

gen-nested-iter-yield-0.1.3 was one of the expected cases failure cases for #120227, due to relying on the exact whitespace used by pretty-printing: see this comment summarizing the crater run. And this comment mentions relnotes.

[apiraino]

WG-prioritization removing prioritization label (Zulip discussion).

If I understand, this breakage was abundantly discussed and approved, so there is no further actionable for us (besides the relnotes). Thanks @nnethercote for the thoroughness in #120227

@rustbot label -I-prioritize