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
t27o: Zig front end, with a round-trip check over our own corpus via gen-zig #8994
Part of the t27o service epic (linked from it). A Zig front end for t27o (lexer, parser and normalisation into the shared middle; see #8966). It goes first because t27 is closest to Zig, and trinity holds hundreds of hand-written .zig files that bees used to port by hand.
Free oracle and corpus: for every ledger spec, .t27 -> t27c gen-zig -> t27o -> .t27' must be behaviourally equivalent: the same test results under the reference and t27b. This tests t27o and also catches generator defects (it would have found #6549 and the CSE hoist, see #8197).
Acceptance: the round-trip pass rate is reported over the 1368 ledger specs, and the trinity .zig coverage table follows the format of #8970.
User Scenarios
Given a ledger spec spec.t27, when t27c gen-zig produces Zig code and t27o parses it back to .t27', then the test results under the reference interpreter and t27b are identical.
Given a Trinity hand-written .zig file, when processed through the new Zig front-end into the shared middle, then normalization succeeds without parser errors.
Activity