zp-static-string-map — static-string-map

ClaimCopy Anchor Link

StringHashMap.get vs StaticStringMap.get (literal keys) under Zig 0.17.0 -Ofast on this Linux machine shows a clear before/after wall-clock gap.

How measuredCopy Anchor Link

• Harness: packages/zperf/examples/bench/evidence_fill.zig (rule zp-static-string-map cases)
• Build: zig build-exe -Ofast · optimize_mode=fast
• Timing: Io.Clock awake; warm=2; median of 9 rounds
• before: string_hashmap_get
• after: static_string_map_get
• ops=200000
• Raw: zp-static-string-map.jsonl

Runtime (this evidence file)Copy Anchor Link

Lint mappingCopy Anchor Link

zperf-lint zp-static-string-map / static-string-map. Default severity in rules.zig is info; see evidence-policy for keep/escalate. Evidence exists and agrees directionally.

VerdictCopy Anchor Link

Agree ~2.53× lookup; Static also zero runtime alloc/init.

LimitsCopy Anchor Link

Only fires when ≥3 literal puts in one function.