Implement iterative parsing to fix deep nesting recursion limits #10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This addresses the deep nesting/recursion limits issue documented in
open-problems.md. The solution converts key parsing and compilation
paths from recursive to iterative approaches using explicit stacks.
Parser changes:
Compiler changes:
The approach was inspired by mquickjs's CPS-style parser, adapted to
Python with a simpler stack-based approach.
Tests now passing:
Still xfail: test_deep_nested_regex_groups (regex parser)
Claude Code transcript: https://gistpreview.github.io/?3c3e6aec285e3d5c2eeb0e2ae02c3a26/index.html