Skip to content

Fix deeply nested authoring terms aborting instead of LLP2001 (AU-03) - #401

Closed
afflom wants to merge 1 commit into
release/v0.4from
fix/issue-374-notation-depth
Closed

afflom wants to merge 1 commit into
release/v0.4from
fix/issue-374-notation-depth

Conversation

@afflom

@afflom afflom commented Nov 3, 2026

Copy link
Copy Markdown
Member

A 50,000-element cons chain in the authoring notation could overflow the compiler stack before semantic JSON decoding. Readable term and type recursion now enforces the existing depth-256 notation bound and reports positioned LLP2001, including when closing parentheses are missing.

AU-03 now checks 50,000-level terms and types through the public API and both human and JSON CLI output. A focused unit test checks exact accepted boundaries and refusal one level beyond them. Independent shallow term-guard and type-guard removal plants fail safely; evidence is recorded in VERIFICATION.md. The existing claim, scenario, SPEC row and generated conformance documentation were updated together.

Validation passed locally: focused nesting unit test; conformance_au_03; all five BDD meta tests; formatting; model audits; specification links; and Clippy for lexlean and repo-conformance with all targets/features and warnings denied. The complete remote gate is pending on this final head.

No embedded compiler-semantics identity input changes, so no language identity or verification oracle regeneration is needed. Targets release/v0.4 as a fix to an existing capability; forward merge to release/v0.5 after landing.

Closes #374.

Enforce the existing depth bound in recursive readable terms and types.
Cover 50,000-level closed and unclosed input through the API and CLI,
exact readable boundaries, and independent guard-removal plants.

Closes #374.

afflom commented Nov 3, 2026

Copy link
Copy Markdown
Member Author

Superseded by the reviewed combined maintenance PR #403 at 39399a2. This PR's exact head bb464d3 is a direct parent of that integration, so its history and implementation are retained. Its approved corrections and verification records are included there.

Closing this duplicate landing path so the combined final tree runs one complete gate. This is not a claim that the work has landed: the linked issues remain open until #403 passes and merges into release/v0.4. Required forward propagation remains tracked by #404/#405.

@afflom afflom closed this Nov 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant