Parse configuration lists without unbounded recursion
Deeply nested synthetic lists exhaust the call stack. Enforce a documented nesting limit.
- Focused work estimate
- 2h 45m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Parsing · Resource limits
Estimated field mix
- Compiler and language tooling70%
- Performance engineering30%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
Fictional build tool Sprig reads a tiny configuration language with identifiers, strings, lists and assignments. Author the grammar and synthetic source corpus locally; parsing never executes source.
Setup prerequisites
- Write the tiny language grammar and generated source examples.
- Create fixtures with Unicode, truncated tokens and nested lists.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Valid nesting parses
- Limit breach gives structured diagnostic
- Parser consumes bounded work after failure
Implementation constraints
- Do not increase runtime stack limits as the fix.
Verification to include
- Parse at supported depth
- Exceed depth limit
Deliverables
- List parser and depth cases
Rollout and recovery
Lower accepted nesting cap if resource behavior is uncertain.
Value of the work
For the engineer: Practice source positions, grammar boundaries and error recovery.
For the team: Inspect whether tooling errors help users correct configuration safely.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.