Function log

test/compute-engine/compile-performance.test.ts:21–25

(...args: unknown[])

 * run uninformative. What a compile-cost test is actually defending against is
 * an algorithmic blowup — a traversal that revisits nodes, or per-compile state
 * that accumulates across calls — and that is visible as a node-visit count,
 * which is identical on every machine. `countCompileVisits` below counts calls
 * to `BaseCompiler.compile`, the single recursive entry point every target's
 * emitter routes through.
 *
 * The execution-speed comparisons further down (compiled runner vs
 * interpreter) are still timed, because there is no counter that can stand in
 * for "the generated code runs faster than the interpreter". They compare two