Tighten parser
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.7k
- Forks
- 249
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 23
Description
The parser is currently pretty loosey-goosey about strictness to any particular language design. For example, you can elide semicolons between adjacent statements. This makes for some confusing issues when a script refuses to run and it's because you missed something that's hard to see.
Before 1.0, it'd be nice to have a pretty straightforward set of grammar rules that are enforced by the parser.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the parser entry point and the existing grammar behavior, using the semicolon example as a concrete case. The issue does not specify the complete grammar rules or name files or tests; done would require an agreed pre-1.0 strict grammar and its enforcement throughout the parser.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100