mirror of
https://github.com/block/buzz.git
synced 2026-08-18 06:50:31 +02:00
npub1qyvc0c5kl4gqv2fd97fsk46tu378sqgy35vc83rvgfwne90sel7s0ed67dandTyler Longwell
410c7f224a
Wren's re-review reproduced a live mutant against the previous test: wrapping the env write in a conditional keeps the trimmed line byte-identical, so a scanner that collects individual lines cannot see control flow — 'unconditional' was an overclaim, and my reported killed mutant was wrong (I mutated the expression on the line, not the shape around it). Renamed to spawn_lazy_pool_env_writes_literal_true_once and rewrote the docs to state exactly what it enforces (literal stays "true"; exactly one write site in runtime.rs) and what it deliberately does not (control flow around the write — the compiler-enforced parameter deletion plus review is the defense there). Both claimed mutants verified red at this head: true->false, and a duplicated write site; clean tree green. Co-authored-by: Tyler Longwell <tlongwell@block.xyz> Signed-off-by: Tyler Longwell <tlongwell@block.xyz>