Context
specs/tri/collections/map.t27 declares module TriMap in 72 lines. 6 of its functions are declared with a body that holds no statement — a signature and a comment where the implementation belongs.
.t27 is the hand-authored source language. t27c compiles it out to C, Rust, Verilog and Zig. You are writing source, not compiler output, and not prose about an implementation.
Current state — re-run these yourself
$ cd /Users/playom/t27
$ ./target/release/t27c gen specs/tri/collections/map.t27 2>&1 | grep -c 'not yet implemented'
6
$ ./target/release/t27c parse specs/tri/collections/map.t27 2>&1 | grep -E '^(recovery-events|declarations-swallowed|lexer-discarded-chars):'
recovery-events: 0
declarations-swallowed: 0
lexer-discarded-chars: 0
Use ./target/release/t27c, not the t27c on PATH: the PATH build prints no parse metrics at all, so the grep above returns nothing and an empty result reads as a pass.
What to write
Keep every signature exactly as it is — the signature is the contract. Quoted verbatim from the file:
- line 23 —
fn empty() -> Map(K, V)
- line 28 —
fn singleton(key: K, value: V) -> Map(K, V)
- line 33 —
fn get(map: Map(K, V), key: K) -> Option(V)
- line 38 —
fn set(map: Map(K, V), key: K, value: V) -> Map(K, V)
- line 43 —
fn keys(map: Map(K, V)) -> []K
- line 48 —
fn values(map: Map(K, V)) -> []V
The file already has 0 test block(s). Add one for each function you implement; a body with nothing asserting on it is a claim, not a result.
Acceptance criteria
-
./target/release/t27c gen specs/tri/collections/map.t27 2>&1 | grep -c 'not yet implemented' prints 0
-
- with criterion 1 satisfied,
./target/release/t27c parse specs/tri/collections/map.t27 2>&1 | grep -E '^(recovery-events|declarations-swallowed|lexer-discarded-chars):' reports 0, 0 and 0
-
- with criterion 1 satisfied, all 6 names above still exist:
grep -cE '^\s*(pub )?fn (empty|singleton|get|set|keys|values)\(' specs/tri/collections/map.t27 prints 6
-
grep -c '^\s*test "' specs/tri/collections/map.t27 prints at least 6 (today: 0)
Boundary
specs/tri/collections/map.t27
Context
specs/tri/collections/map.t27declares moduleTriMapin 72 lines. 6 of its functions are declared with a body that holds no statement — a signature and a comment where the implementation belongs..t27is the hand-authored source language.t27ccompiles it out to C, Rust, Verilog and Zig. You are writing source, not compiler output, and not prose about an implementation.Current state — re-run these yourself
Use
./target/release/t27c, not thet27con PATH: the PATH build prints no parse metrics at all, so the grep above returns nothing and an empty result reads as a pass.What to write
Keep every signature exactly as it is — the signature is the contract. Quoted verbatim from the file:
fn empty() -> Map(K, V)fn singleton(key: K, value: V) -> Map(K, V)fn get(map: Map(K, V), key: K) -> Option(V)fn set(map: Map(K, V), key: K, value: V) -> Map(K, V)fn keys(map: Map(K, V)) -> []Kfn values(map: Map(K, V)) -> []VThe file already has 0
testblock(s). Add one for each function you implement; a body with nothing asserting on it is a claim, not a result.Acceptance criteria
./target/release/t27c gen specs/tri/collections/map.t27 2>&1 | grep -c 'not yet implemented'prints0./target/release/t27c parse specs/tri/collections/map.t27 2>&1 | grep -E '^(recovery-events|declarations-swallowed|lexer-discarded-chars):'reports 0, 0 and 0grep -cE '^\s*(pub )?fn (empty|singleton|get|set|keys|values)\(' specs/tri/collections/map.t27prints6grep -c '^\s*test "' specs/tri/collections/map.t27prints at least6(today: 0)Boundary
specs/tri/collections/map.t27