Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Validate what the grammar leaves to a later stage

Open
  • Is something wrong?
#116 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
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
compilers

Research direction

Start by reading the grammar and validation flow in the boltlang-parser and boltlang-hir-def crates to see which checks are deferred to later stages. Trace how struct literals, let expressions, and $x:frag specifiers are handled. Done means these three invalid forms are reported while valid forms continue to parse or validate.

Written by the indexing model from the issue text.

Description

enhancement scope:diagnostics scope:syntax

The grammar accepts some things that aren't valid, and nothing reports them yet:

  • ..base in a struct literal must come last;
  • a let expression only makes sense in a condition;
  • the fragment specifier of $x:frag can be any identifier.

Crates: boltlang-parser, boltlang-hir-def.

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

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.