Implement the 1 empty function body in specs/test_framework/graph_drift_detection.t27
Context
specs/test_framework/graph_drift_detection.t27 is 650 lines long. 1 of its functions is 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
$ t27c gen specs/test_framework/graph_drift_detection.t27 2>&1 | grep -c 'not yet implemented'
1
$ t27c spec-status specs/test_framework/graph_drift_detection.t27
NOPARSE
Use 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 77 -
fn default_drift_config() -> DriftConfig
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
-
t27c gen specs/test_framework/graph_drift_detection.t27 > /tmp/t27-gen.zig && grep -c 'not yet implemented' /tmp/t27-gen.zig prints 0 (today: 1)
-
t27c spec-status specs/test_framework/graph_drift_detection.t27 does not print NOPARSE - the file still parses. (This replaces a parse-metrics criterion. The compiler in the container prints no such metrics, so the command printed nothing and no work could ever satisfy it.)
-
- with criterion 1 satisfied, all 1 name above still exist:
grep -cE '^\s*(pub )?fn (default_drift_config)\(' specs/test_framework/graph_drift_detection.t27 prints 1
-
grep -cE '^[[:space:]]*test[[:space:]]+("|[A-Za-z_])' specs/test_framework/graph_drift_detection.t27 prints at least 1 (today: 7)
Boundary
specs/test_framework/graph_drift_detection.t27
Implement the 1 empty function body in specs/test_framework/graph_drift_detection.t27
Context
specs/test_framework/graph_drift_detection.t27is 650 lines long. 1 of its functions is 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
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 default_drift_config() -> DriftConfigThe 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
t27c gen specs/test_framework/graph_drift_detection.t27 > /tmp/t27-gen.zig && grep -c 'not yet implemented' /tmp/t27-gen.zigprints0(today: 1)t27c spec-status specs/test_framework/graph_drift_detection.t27does not printNOPARSE- the file still parses. (This replaces a parse-metrics criterion. The compiler in the container prints no such metrics, so the command printed nothing and no work could ever satisfy it.)grep -cE '^\s*(pub )?fn (default_drift_config)\(' specs/test_framework/graph_drift_detection.t27prints1grep -cE '^[[:space:]]*test[[:space:]]+("|[A-Za-z_])' specs/test_framework/graph_drift_detection.t27prints at least1(today: 7)Boundary
specs/test_framework/graph_drift_detection.t27