Repository navigation
docs: front-end 'essentially complete' is true of the corpora it measured, and a second corpus has found two gaps - #944
Merged
Conversation
…ured, and a second corpus has since found two gaps CONFORMANCE-LIBRARIES.md closes with "Front-end (parse + compile) is essentially complete", and sends the reader on to the runtime surface. That report is dated 2026-06-27 and its measurement stands: it is about the lib/ trees of ten released gems plus Rails and Puppet, where rbgo reaches 99.82% / 100% with 0 over-permissive. What it cannot see is a construct those codebases do not write. ruby/spec does write them, and two parser defects are open against it: #669 a do...end block inside an arrow-lambda body, after a paren-less command call -- 160 ruby/spec examples, the largest single-defect figure in the tracker #905 a brace block on a name that is also a local, inside parentheses Neither contradicts the June figures. #669 is a NESTING of the paren-less-command-plus-do...end form that the report's own "What moved the needle" records as fixed, so the fix and the defect are different shapes of one construct. ⚠ And one thing stated as unchecked rather than assumed: whether any of the 6 remaining Rails gaps IS that construct has not been cross-referenced. A first draft of this change asserted that no file in Rails, Puppet or the ten gems nests it that way -- which is plausible (such a file would have shown up as a gap) and which I had not measured. It is now written as the open question it is, because "not checked" and "known absent" are not the same claim and the difference is half an hour of work. The lesson the paragraph carries: "essentially complete" was true of what was asked, and a corpus answers only the questions it contains. Refs #669, #905, #941 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
docs: "front-end essentially complete" is true of the corpora it measured, and a second corpus has since found two gaps
CONFORMANCE-LIBRARIES.md closes with "Front-end (parse + compile) is essentially
complete", and sends the reader on to the runtime surface. That report is dated
2026-06-27 and its measurement stands: it is about the lib/ trees of ten released
gems plus Rails and Puppet, where rbgo reaches 99.82% / 100% with 0
over-permissive.
What it cannot see is a construct those codebases do not write. ruby/spec does
write them, and two parser defects are open against it:
#669 a do...end block inside an arrow-lambda body, after a paren-less
command call -- 160 ruby/spec examples, the largest single-defect
figure in the tracker
#905 a brace block on a name that is also a local, inside parentheses
Neither contradicts the June figures. #669 is a NESTING of the
paren-less-command-plus-do...end form that the report's own "What moved the
needle" records as fixed, so the fix and the defect are different shapes of one
construct.
⚠ And one thing stated as unchecked rather than assumed: whether any of the 6
remaining Rails gaps IS that construct has not been cross-referenced. A first
draft of this change asserted that no file in Rails, Puppet or the ten gems
nests it that way -- which is plausible (such a file would have shown up as a
gap) and which I had not measured. It is now written as the open question it is,
because "not checked" and "known absent" are not the same claim and the
difference is half an hour of work.
The lesson the paragraph carries: "essentially complete" was true of what was
asked, and a corpus answers only the questions it contains.
Refs #669, #905, #941
Co-Authored-By: Claude Opus 5 noreply@anthropic.com