Add Expr
support to ControlFlowOp
representation
#10358
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This commit allows
IfElseOp
andWhileLoopOp
to have acondition
that is anExpr
typedBool()
, andSwitchCaseOp
to have atarget
that is anExpr
. It does not fully add support to resolving these new allowed values into the control-flow builder interface (that will come later).Details and comments
Close #10224.
Depends on #10332. Same consideration about release note.
Originally I was doing the control-flow builder interface as part of this commit as well since there's very little additional work needed to make that work. In practice, though, being able to test the builder interface requires a bunch of the
DAGCircuit
-related bits to be working as well, so I've split it off.