Fix qasm generation/parsing for classical controls #5434
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dabacon
requested changes
Jun 6, 2022
daxfohl
commented
Jun 6, 2022
Collaborator
Author
|
@dabacon I fixed the recommendations. Should this be merged before 0.15? |
dabacon
approved these changes
Jun 27, 2022
rht
pushed a commit
to rht/Cirq
that referenced
this pull request
May 1, 2023
harry-phasecraft
pushed a commit
to PhaseCraft/Cirq
that referenced
this pull request
Oct 31, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Fixes #5388
QASM does not support
!=relations required by (Measurement)KeyConditions. Thus we change parsing and QASM generation to use SympyConditions withsympy.Eq(sympy.Symbol(key), value)relation, and drop the (invalid) QASM generation for KeyConditions.All qasm in these tests was also tested against qiskit for validity.