Skip to content

[WIP] Arc PyDAGCircuit - #16630

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

[WIP] Arc PyDAGCircuit#16630
raynelfss wants to merge 23 commits into
Qiskit:mainfrom
raynelfss:split-py-dag-arc

Conversation

@raynelfss

Copy link
Copy Markdown
Contributor

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:

raynelfss and others added 23 commits June 22, 2026 18:12
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.
The following commits make sure we preserve the metadata of the `DAGCircuit` in passes where the instance is copied. This includes:
- `CommutativeOptimization`
- `ConvertToPauliRotations`
- `DisjointLayout`
- `ElidePermutations`
- `LitinskiTransformation`
- `Split2QUnitaries`
- `TwoQubitPeepholeOptimization`
- `BasisTranslator`
- `SabreLayout`
- `SabreRouting`
- `UnitarySynthesis`
This commit moves the `name` attribute to exist only within `PyDAGCircuit` since it is Python exclusive metadata.
This commit also adds constructors with metadata from other `PyDAGCircuit` instances and a `DAGCircuit` from rust:
- `from_dagcircuit` which also accepts optional `metadata` and `name`.
- `from_dagcircuit_with_cloned_metadata` which accepts a reference to the `PyDAGCircuit` and copies over the attributes for the user.
The transpiler passes that don't perform transformations in place have been updated to use this model.
Some auxiliary methods would need to immutably or mutably obtain the dag and therefore should only remain as auxiliary methods to the `DAGCircuit` instead of the `PyDAGCircuit` instance.
The methods will now be called `try_read` and `try_write` and are fallible. This commit refactors the methods and updates their usage.
- This introduces a clone which we will try and resolve later.
Provisionally this method has been split to have a python version, although the original is not fully independent of Python either. This allows the C API version to avoid using `PyDAGCircuit`.
These attributes are all public, so no need to provide immutable views.
The folllowing commti replaces the internals of `PyDAGCircuit` to include an atomic-reference-counted cell that encloses a Read-Write Lock to guarantee that the `DAG` instance may still be mutable afterwards.

This commit doesn't work on its own and a follow-up commit fixing the behavior of `PyDAGCircuit` on every transpiler pass.
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.

1 participant