Implement the 8 empty function bodies in specs/tri/collections/bitvector.t27

[gHashTag]

Context

specs/tri/collections/bitvector.t27 declares module TriBitvector in 92 lines. 8 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
$ t27c gen specs/tri/collections/bitvector.t27 2>&1 | grep -c 'not yet implemented'
8
$ t27c spec-status specs/tri/collections/bitvector.t27
IMPLEMENTED

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:

1. line 23 — fn empty() -> BitVector
2. line 28 — fn with_capacity(bits: usize, allocator: std.mem.Allocator) -> !BitVector
3. line 33 — fn push(bv: *BitVector, bit: bool, allocator: std.mem.Allocator) -> !void
4. line 38 — fn pop(bv: *BitVector) -> ?bool
5. line 43 — fn get(bv: BitVector, index: usize) -> bool
6. line 48 — fn set(bv: *BitVector, index: usize, value: bool) -> void
7. line 53 — fn len(bv: BitVector) -> usize
8. line 58 — fn append(bv: *BitVector, other: BitVector, allocator: std.mem.Allocator) -> !void

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

• 1. t27c gen specs/tri/collections/bitvector.t27 > /tmp/t27-gen.zig && grep -c 'not yet implemented' /tmp/t27-gen.zig prints 0
• 2. t27c spec-status specs/tri/collections/bitvector.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.)
• 3. with criterion 1 satisfied, all 8 names above still exist: grep -cE '^\s*(pub )?fn (empty|with_capacity|push|pop|get|set|len|append)\(' specs/tri/collections/bitvector.t27 prints 8
• 4. grep -cE '^[[:space:]]*test[[:space:]]+("|[A-Za-z_])' specs/tri/collections/bitvector.t27 prints at least 8 (today: 19)

Boundary

specs/tri/collections/bitvector.t27

[gHashTag]

Closing as done: this issue's acceptance criteria are satisfied on master today, measured with a t27c built from master at f566a48:

$ t27c spec-status specs/tri/collections/bitvector.t27
IMPLEMENTED
$ t27c gen specs/tri/collections/bitvector.t27 > /tmp/t27-gen.zig && grep -c 'not yet implemented' /tmp/t27-gen.zig
0
$ grep -cE '^[[:space:]]*test[[:space:]]+("|[A-Za-z_])' specs/tri/collections/bitvector.t27
19

The bodies are written and the file carries tests. Whichever attempt landed them, the work this issue asked for is in the tree, so it is not fuel for another bee.

Found by queen verify-issue, which re-runs every command an issue quotes against origin/master; the two files where it disagreed with the compiler stay open.