uber / h3-go / 39290561686

100%

master: 100%

Pull #170

github

conformance: drop derivable disks from traversal, flag identity uncompacts

Two files repeated data they already contained. Every traversal record
carried disk1 to disk3 and diskDistances2 next to ring1 to ring3, and a
k-disk is the origin plus the rings 1 to k, so on all 542 lines the disks
and the grouped disk were exactly the rings rearranged; they were 63% of
the file. Half the sets records asked uncompactCells for the input's own
resolution, where the output is the input as a set, and wrote it out
again; uncompact was 52% of that file.

Traversal records now carry the rings only. A consumer builds the k-disk
as the cell and rings 1 to k and the distance-grouped disk as those rings
in order, and checks gridDisk and gridDiskDistances against them; the Go
runner now does so for k 1 to 3 instead of k 2 alone. What the dropped
keys verified was that two reference functions agree with each other,
which is not the suite's job. The file goes from 1.20 MB to 0.42 MB.

Sets records write uncompact as true when the output equals the input
with padding removed, sorted and deduplicated, and still write the set or
the error otherwise; 896 of 1,344 lines take the flag. The runner
compares against the normalised input in that case. The file goes from
1.47 MB to 1.15 MB; input stays, since it is the test's argument.

Both are removals of keys a consumer may have read, so the format version
moves to h3-conformance/2; the README notes under each stream what format
1 carried. The generator gains normalizeSet, which printIndexSet already
did inline, to compare the two sets.

Flipping one ring entry by hand makes the runner report GridRing,
GridDisk and GridDiskDistances for that k and above; replacing one true
with a wrong set makes it report UncompactCells. Regeneration from the
unchanged library changes only the traversal and sets files, the
traversal curated file and the manifest; the digests are untouched.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

11 of 18 new or added lines in 1 file covered. (61.11%)

4562 of 4569 relevant lines covered (99.85%)

4150938.21 hits per line