[charliermarsh]

Summary

match is a soft keyword. It can name a variable, a function, or the target of an annotated assignment, including after a semicolon.

first(); match = value
first(); match(value)
first(); match[0]: int

The parser reported a compound-statement error as soon as it saw the match token. We now check the preceding separator when parsing a match statement. If the token turns out to be an identifier, speculative parsing discards the diagnostic. A genuine match statement on the same logical line still produces the original error.

[astral-automations-bot]

Memory usage report

Memory usage unchanged ✅

---

Results for 565a712 · Workflow run

[astral-automations-bot]

ecosystem-analyzer results

No diagnostic changes detected ✅

Full report with detailed diff · Timing results

---

Results for 565a712 · Workflow run

[astral-automations-bot]

ruff-ecosystem results

Linter (stable)

✅ ecosystem check detected no linter changes.

Linter (preview)

✅ ecosystem check detected no linter changes.

Formatter (stable)

✅ ecosystem check detected no format changes.

Formatter (preview)

✅ ecosystem check detected no format changes.

---

Results for 565a712 · Workflow run

[codspeed]

Merging this PR will not alter performance

✅ 274 untouched benchmarks
⏩ 14 skipped benchmarks¹

---

_{Comparing fix/semicolon-match-names (565a712) with main (4549e31)}

Footnotes

1. 14 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[MichaReiser]

I don't think we should track this in the Lexer. It results in a write on the hot lex_token path, without being needed in most cases.