Fewer errors after a missing `;`

Open
  • Is something wrong?
#114 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
backend

Research direction

Start by reading the error recovery logic in the boltlang-parser crate and the parser tests that cover missing semicolons. Compare how recovery currently reports unexpected tokens with the rust-analyzer behavior mentioned in the issue. Done means badly broken input produces fewer follow-on errors after a missing ;; the issue does not specify an exact threshold or test file.

Written by the indexing model from the issue text.

Description

enhancement scope:diagnostics scope:syntax

Error recovery reports one error per unexpected token after a missing ;, like rust-analyzer. That can be noisy for badly broken input.

Crates: boltlang-parser.

Dominant language
Rust
Stars
54
Forks
3
Avg merge
7m
Merged PRs (30d)
29

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from boltlang/Bolt

All issues in boltlang/Bolt

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.