-
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
Add missing equivalences for XX{Plus,Minus}YYGate #9017
Conversation
These are just copied from the `_define` method on the classes. The equivalence-library tests are updated (since `subTest` doesn't isolate correctly with `testtools`) to print out all the names of the tests being run, so it's clear that the existing test now tests these definitions.
Thank you for opening a new pull request. Before your PR can be merged it will first need to pass continuous integration tests and be reviewed. Sometimes the review process can be slow, so please be patient. While you're waiting, please feel free to review other open PRs. While only a subset of people are authorized to approve pull requests for merging, everyone is encouraged to review open pull requests. Doing reviews helps reduce the burden on the core team and helps make the project's code better for everyone. One or more of the the following people are requested to review this: |
Pull Request Test Coverage Report for Build 3345143334
💛 - Coveralls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍🏻 Would it make sense to automatically add the default decomposition of gates into the equivalence library instead of copy+pasting the actual definition? Or maybe the other way around: <SomeStandardGate>._define
invokes the equivalence library and runs that (but maybe this way around it's too slow...)
I think (but am speaking purely from my own views) that the general direction we're heading in is to have the equivalence library be the primary source of definitions for gates, at least, and (This gate would already have been fine in |
Summary
These are just copied from the
_define
method on the classes. The equivalence-library tests are updated (sincesubTest
doesn't isolate correctly withtesttools
) to print out all the names of the tests being run, so it's clear that the existing test now tests these definitions.Details and comments
Bonus points to anyone who already knew the esoteric Python scoping rules that forbade me from using a list comprehension to define the test parametrisation here.