Default HybridEngine to the Rust classical interpreter, with parity fixes and #345 engine fail-fast by ciaranra · Pull Request #347 · PECOS-packages/PECOS

Fail fast on invalid definitions and out-of-range measurement writes, and make the no-return measurement index absolute across batches (#345)

ciaranra

committed

Revive orphaned pecos-phir-json integration tests by wiring them to top-level and reconciling stale value-representation expectations

ciaranra

committed

Merge remote-tracking branch 'origin/dev' into phir-engine-fail-fast

ciaranra

committed

Fix WASM integration tests declaring i32 registers at invalid size 32 (signed i(S+1) needs size <= 31), exposed by the new fail-fast on invalid definitions

ciaranra

committed

Default HybridEngine's classical interpreter to the Rust implementation

ciaranra

committed

Strengthen Rust-Python parity coverage: nested/unary fuzz, 10x more fuzz iterations, and a QASM-generated-PHIR differential

ciaranra

committed

Reject undeclared classical variables in the Rust PHIR core and add a foreign_func_calls collector

ciaranra

committed

Match the Python interpreter's validation, error types, and foreign-call checks in the Rust wrapper

ciaranra

committed

Add Rust/Python parity tests for exception types and undeclared-variable errors

ciaranra

committed

Document the default classical-interpreter switch and the cinterp='python' escape hatch

ciaranra

committed

Fix unused-argument lint in the parity test's foreign-object stub

ciaranra

committed

Fail fast on measurement writes beyond declared register size and on conflicting variable redefinitions

ciaranra

committed

Support detaching the foreign object for multiprocessing and give phir_validate a clear error on standalone installs

ciaranra

committed

Add run_multisim and modulo-by-zero parity regression tests; name the PyPHIR limitation in the docstring

ciaranra

committed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Default HybridEngine to the Rust classical interpreter, with parity fixes and #345 engine fail-fast#347

Default HybridEngine to the Rust classical interpreter, with parity fixes and #345 engine fail-fast#347
ciaranra merged 14 commits into
devfrom
phir-engine-fail-fast

Commits on Jul 10, 2026

Fail fast on invalid definitions and out-of-range measurement writes, and make the no-return measurement index absolute across batches (#345)

Revive orphaned pecos-phir-json integration tests by wiring them to top-level and reconciling stale value-representation expectations

Merge remote-tracking branch 'origin/dev' into phir-engine-fail-fast

Fix WASM integration tests declaring i32 registers at invalid size 32 (signed i(S+1) needs size <= 31), exposed by the new fail-fast on invalid definitions

Default HybridEngine's classical interpreter to the Rust implementation

Strengthen Rust-Python parity coverage: nested/unary fuzz, 10x more fuzz iterations, and a QASM-generated-PHIR differential

Reject undeclared classical variables in the Rust PHIR core and add a foreign_func_calls collector

Match the Python interpreter's validation, error types, and foreign-call checks in the Rust wrapper

Add Rust/Python parity tests for exception types and undeclared-variable errors

Document the default classical-interpreter switch and the cinterp='python' escape hatch

Fix unused-argument lint in the parity test's foreign-object stub

Fail fast on measurement writes beyond declared register size and on conflicting variable redefinitions

Support detaching the foreign object for multiprocessing and give phir_validate a clear error on standalone installs

Add run_multisim and modulo-by-zero parity regression tests; name the PyPHIR limitation in the docstring