3.9. Measured evidence🔗

The repository includes paired scanner/reference benchmarks for Graph, Decimal, and IPv6, plus the Cedar conformance suite. In one local development build, the generated one-scan parser was 2.8x faster than the old gated parser for Decimal, 2.7x faster for a full IPv6 address, and 2.9x faster for a compressed IPv6 address. The lower-level scanner/reference comparison ranged from 1.2x on compressed IPv6 to 270x on the largest Graph case; that wider range reflects how much candidate materialization each grammar triggers.

Run the same comparisons locally:

cd other-examples && lake exe parser_benchmark
cd cedar-examples && lake exe scanner_benchmark
cd cedar-examples && lake build ConformanceTests

Timings vary by machine and build mode, so CI does not enforce a fixed speedup. Each benchmark checks that both engines accept the same number of iterations, while Triptych.scan_eq_decode and the generated parser contracts provide the machine-checked correctness evidence.