You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
rbgo refuses a script with arguments: no program using ARGV can run, and the corpus cannot see it #708
So the VM half is in place and the argument vector simply never reaches it. MRI's
contract is ruby [options] script.rb [arguments...], with everything after the
script path belonging to the program, and -- forcing that boundary.
Why this matters more than its example count
Nothing in the ruby/spec corpus sweep exercises it, so it is worth zero
conformance examples and would never surface in the ratchet. But it is
load-bearing for what this project is for: rbgo build --closed script.rb
produces a standalone binary, and a standalone binary that cannot be passed
arguments is not a usable program. Any CLI tool, any script with a filename
parameter, any OptionParser program is out of reach.
It was found as a measurement hazard, which is how I would expect it to be met:
an agent's probe used ARGV[0] to pass a file path, and every single case returned
the same "LOAD_ERR". A uniform verdict across differing inputs was the only signal —
had the probe varied for another reason, the whole MRI → rbgo direction of that
measurement would have been silently void.
This is the fourth front-end gap found today, and they share a shape
In each case the VM was further along than the front-end, and in each case the gap
is invisible to the conformance ratchet because the ratchet invokes rbgo <file>
with no arguments and reads a printed result line. The corpus cannot see the
command-line surface at all, so that surface needs its own tests rather than
waiting for an example count to justify it.
Activity
Give rbgo a ruby command line: ARGV, $0 and -w/-W (#708, #709) (#716)