Repository navigation
Say what the unswept trees hold, now that they have been measured - #39
Merged
Merged
Conversation
The page said the unswept trees are "not run at all" and stopped there,
which leaves a reader unable to tell whether the unmeasured half of
ruby/spec is a rounding error or the bulk of the work.
Measured once on 2026-11-10 against MRI 4.0.7 through the same shim — a
dated run, said to be one, and not a gate. The gap across the 970 files
where the two engines differ is 2,341 examples, and the shape matters
more than the size:
- 78 files cannot be measured at all: every command_line/ spec is built
on ruby_exe and optional/capi needs a compiled C extension, so MRI
itself scores zero in them;
- the largest single debt is a HANG rather than a missing feature —
Net::FTP is 442 examples behind with 39 of its 56 files killed by the
clock on rbgo and none on MRI;
- the outright absences are comparatively small (Coverage 53, WeakRef 9).
Verified with the pinned command this lane runs:
$ go run github.com/go-embedded-ruby/docs/tools/[email protected] --root .
6 total claim(s), 1 version claim(s) and 3 stubbed-helper mention(s) checked
against the gate's 23672 at Ruby 4.0.9 (derived from RUBY_VERSION);
the shim stubs output_to_fd, ruby_cmd, ruby_exe
Co-Authored-By: Claude Opus 5 <[email protected]>
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.
The page said the unswept trees are "not run at all" and stopped there. That is honest and useless on its own: a reader cannot tell whether the unmeasured half of ruby/spec is a rounding error or the bulk of the work.
They have now been measured once, on 2026-11-10, against MRI 4.0.7 through the same shim — a dated run, said on the page to be one, and not a gate.
Across the 970 files where the two engines differ the gap is 2,341 examples, and the shape matters more than the size:
command_line/spec is built onruby_exe, andoptional/capineeds a compiled C extension — MRI itself scores zero in them. That share asks for harness work, not interpreter work.Net::FTPis 442 examples behind, with 39 of its 56 files killed by the clock on rbgo and none on MRI.Coverage53 examples,WeakRef9.Verified with the pinned command this lane runs:
Refs go-embedded-ruby/ruby#916 — it stays open; this page only stops leaving the
reader to guess what the unswept half contains.
🤖 Generated with Claude Code