Qiskit / qiskit / 37006712768

88%

main: 88%

Build Type

push

github

Committed by web-flow

Commit Message

Add implementation of IR handle extraction (#17103)

* Add implementation of IR handle extraction

This is unused in this commit, but is the extraction logic for creating
an internal dynamic implementation of "how to expose this object to
Python", which will be held by passes and the Rust--Python `PassManager`
boundary.

* Split `QuantumCircuit` and `CircuitData` as IRs

There is a significant difference in Python space between the full
`QuantumCircuit` and `CircuitData` IRs, namely `QuantumCircuit.layout`.
The previous system of automatically converting from one to the other in
the native layout _always_ threw away the `layout`, with no way to write
passes on `QuantumCircuit` (or more likely, converting to it at the end)
that didn't throw it away again at the termination of the pass.  By
making a separation between `CircuitData` and `QuantumCircuit`, using
the existing `QuantumCircuit._data` public API field, and requiring an
explicit lowering pass, we push the burden of managing the
Python-specific state into Python-aware passes.

In order to allow custom passes to spell the IR type of
`QuantumCircuit._data`, we have to add the name `CircuitData` to the
public API.

* Add `QuantumCircuit.from_circuit_data` to API

Since we already made `CircuitData` a nameable type that implements
`IR`, we need a way to get back to a full `QuantumCircuit` to complete
the interop story there.

Coverage Stats

30 of 117 new or added lines in 6 files covered. (25.64%)

8 existing lines in 3 files now uncovered.

122883 of 139520 relevant lines covered (88.08%)

940054.1 hits per line