Skip to content

fix(diagnostics): clearer wording, coalesced recovery, accurate capture sites#534

Merged
zharinov merged 1 commit into
masterfrom
diagnostics-quality-pass
Jun 29, 2026
Merged

fix(diagnostics): clearer wording, coalesced recovery, accurate capture sites#534
zharinov merged 1 commit into
masterfrom
diagnostics-quality-pass

Conversation

@zharinov

Copy link
Copy Markdown
Member

Summary

  • A run of stray tokens inside (...), [...], or {...} collapses into one error instead of one per token.
  • A missing ), ], or } reports one uniform "unclosed" message.
  • Several type and shape error headlines now use plain language, e.g. a repeated capture must be collected into a list.
  • Capture-conflict errors mark only the real top-level captures, not ones inside nested scopes like {...} @row. The suggested row-capture name also skips names already used nearby.
  • run and trace use the last definition when --entry is omitted.

Why

Some diagnostics read like internal jargon, two pointed at the wrong code, and a query with several definitions errored instead of running its last one.

Notes

  • The last-definition default is documented in docs/lang-reference.md and covered by a CLI test.
  • fuzz_no_panic.proptest-regressions pins a parser input (("¡;) that the recovery change fixed.

…re sites

- Parser recovery groups a run of stray tokens into one error node and one
  diagnostic instead of one per token; a missing ) ] } reports a uniform
  "unclosed" message via expect_close.
- Reworded several type/shape error headlines into plain language.
- capture_sites no longer flags captures inside nested scopes like {...} @Row,
  and the suggested row-capture name skips names already bound in scope.
- run/trace default to the last definition when --entry is omitted.
@zharinov
zharinov enabled auto-merge (squash) June 29, 2026 17:22
@zharinov
zharinov merged commit b92e9e9 into master Jun 29, 2026
4 checks passed
@zharinov
zharinov deleted the diagnostics-quality-pass branch June 29, 2026 17:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant