-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implementation of classical expressions: RFC 10 #10239
Comments
As of right now, there are PRs open for every "feature" component of the new |
Here's the review order for the PRs under this issue:
|
This epic is now complete for the purposes of Terra 0.25.0rc1. I'll leave it open for the time being because it's tracking a couple more things for the final 0.25.0, but in principle it's complete from a feature perspective. |
With this epic closed, can https://github.com/Qiskit/RFCs/blob/master/0010-simple-classical-representations.md be considered |
Yes |
What should we add?
This is the tracking epic for RFC 10: preliminary representation of classical expressions. Details of the proposal are in the linked document.
Required
SwitchCaseOp
,WhileLoopOp
andIfElseOp
qiskit-terra#10224QuantumCircuit
andDAGCircuit
methods involvingExpr
expressions qiskit-terra#10233Expr
andType
values in QPY serialisation qiskit-terra#10289Expr
values to OpenQASM 3 qiskit-terra#10225Expr
values through the transpiler pipelines qiskit-terra#10234Expr
andType
work qiskit-terra#10331Strongly desired for 0.25
Expr
values in the control-flow builder interface qiskit-terra#10228Long term required, not necessary for 0.25
Expr
values toSabreSwap
andSabreLayout
qiskit-terra#10232Expr
values in control flow #10236Expr
values qiskit-terra#10238The text was updated successfully, but these errors were encountered: