Skip to content

[WIP] Split PyDAGCircuit and DAGCircuit#16471

Draft
raynelfss wants to merge 2 commits into
Qiskit:mainfrom
raynelfss:split-py-dag
Draft

[WIP] Split PyDAGCircuit and DAGCircuit#16471
raynelfss wants to merge 2 commits into
Qiskit:mainfrom
raynelfss:split-py-dag

Conversation

@raynelfss

Copy link
Copy Markdown
Contributor

Fixes #15575
The following commit splits the representations of DAGCircuit into:

  • DAGCircuit representing the rust-native implementation of the DAG excluding its metadata.
  • PyDAGCircuit the version that gets exposed to Python.

PyDAGCircuit does not implement Deref<DAGCircuit> due to future plans requiring us to implement a reference counted Circuit for the Python version of the DAG.

This is a work in progress and needs a lot of extra combing and detangling.

AI/LLM disclosure

  • I didn't use LLM tooling, or only used it privately.
  • I used the following tool to help write this PR description:
  • I used the following tool to generate or modify code:

The following commit splits the representations of `DAGCircuit` into:
- `DAGCircuit` representing the rust-native implementation of the `DAG` excluding its metadata.
- `PyDAGCircuit` the version that gets exposed to Python.

`PyDAGCircuit` does not implement `Deref<DAGCircuit>` due to future plans requiring us to implement a reference counted `Circuit` for the Python version of the DAG.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Separate PyDAGCircuit and PyCircuitData

1 participant