Repository navigation
comline-reference: the Rust runtime answers encode/decode questions over stdio - #34
Merged
Merged
Conversation
added 3 commits
October 25, 2026 14:30
…ver stdio A new workspace member, runtime/reference: newline-delimited JSON on stdin and stdout, in the conformance corpus's own encoding, so any vector case is a valid request. Requests batch, many to a line. Also `check`, for a fuzzer to validate a generated type and value, and `version`. The integration test replays every vector through the built binary, one batch per file.
…efusal `answer` reports it as a reject, which a fuzzer would count as a real one.
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.
Stacked on #32. Part of runtime#29 stage 1 (step R3).
runtime/reference(comline-reference,publish = false): a binary plus a small lib holding the protocol, so it's tested in-process.op/input/bytesis a valid request. A line is one request or a batch (array); the reply has the same shape and order.bytes→{id, bytes}; withbytes→{id, accept: true, input}or{id, accept: false}; otherwisenot_implementedorerror. A malformed line gets anerrorreply (idnull if unparseable) and the process keeps going. EOF exits 0.check(validates a generated type/value pair) andversion(protocol: 1, crate version, ops, formats, framings).tests/process.rsspawns the built binary and replays every case of everyvectors/*.json, one batch per file, withrun's semantics; plus a malformed-line test.runtime/reference/README.md(protocol, examples, stability: ops append-only underprotocol: 1), and a pointer from the conformance README.