wai-quantum 0.6.5 and the service: programs that measure in the middle #335
Loading…
Reference in a new issue
No description provided.
Delete branch "wai/quantum-dynamic-circuits"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Programs that measure in the middle, reset after a gate, or act on measured bits now run on the service. The library (wai-quantum 0.6.5) gains the two primitives they need. Additive: every pinned digest is unchanged, and a program that measures only at the end runs exactly as before.
Library
Tableau::measure(a, random)measures a qubit of the wide tableau and leaves the state the outcome selects (Aaronson–Gottesman).Tableau::is_random(a)answers with a single column scan.StateVector::probability_one(a fixed-chunk sum, so the same at any thread count) andStateVector::collapse.Service
qasm::Instr): measurement andresetanywhere;if (c[0]) …,if (!c[0]) …,if (c == 3) { … } else { … }; OpenQASM 2'sif(c==n) gate;;bit b = measure q;.src/dynamic.rs): such a program runs onstatevectororstabilizer.autopicks the tableau when every gate is Clifford.Checks run on the build host, on the tree merged with main
--all-targetson wai-quantum reports pre-existing findings in other files.scripts/check-lockfiles.shpasses.Lockfiles. wai-quantum is 0.6.5 in every workspace that pins it. Cargo's rewrite of wai-rs's lock also re-picks two Windows-only edges (windows-sys 0.52, getrandom 0.3), and both versions were already in the lock.
Note for the reviewer: an unrelated, pre-existing failure. On #331,
energy receipts · linux-arm64failedquantum_noisy::tests::branching_runs_depend_on_neither_threads_nor_the_state_limit. At 16 qubits, the run limited to 1 state differs slightly from the 64-state run.🤖 Generated with Claude Code
ifis no longer the refusal example; teleportation checks the dynamic path