Fix incorrect PPM-PPR match in CommuteCliffordPastPPM#1590
Merged
Conversation
- Updated `verifyNextNonClifford` and `verifyPrevNonClifford` functions to streamline user operation checks. - Removed redundant checks - Minor formatting adjustment in `ppr_to_ppm` function docstring
Contributor
|
Hello. You may have forgotten to update the changelog!
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Context:
Fixed a bug in the verification logic of CommuteCliffordPastPPM and updated the docstring.
Previously, in cases like:
The
ppmwas incorrectly matched with the firstppr, even though%0:2dominates%1and%1dominates%2:2.Description of the Change:
verifyNextNonCliffordandverifyPrevNonCliffordfunctions to streamline user operation checks.ppr_to_ppmfunction docstringBenefits: