Repository navigation
Conversation
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.
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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A 50,000-element
conschain 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 positionedLLP2001, 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.