-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Improve docstring for Statevector.evolve
#9666
Conversation
I didn't realize from the generated documentation that `Statevector.evolve` can accept an `Instruction` or `QuantumCircuit`, not just an `Operator`. I only learned it once I found myself reading the source. This modifies the docstring to make it explicit.
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 4307079157
💛 - 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.
Nice, thanks Jim.
@@ -360,7 +360,7 @@ def evolve(self, other, qargs=None): | |||
"""Evolve a quantum state by the operator. | |||
|
|||
Args: | |||
other (Operator): The operator to evolve by. | |||
other (Operator | QuantumCircuit | Instruction): The operator to evolve by. |
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.
Oh, Sphinx is actually complaining about the lookup of Instruction
is ambiguous. I think if you make it circuit.Instruction
it should be happy again.
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.
Thanks, that worked. 🙂
* Improve docstring for `Statevector.evolve` I didn't realize from the generated documentation that `Statevector.evolve` can accept an `Instruction` or `QuantumCircuit`, not just an `Operator`. I only learned it once I found myself reading the source. This modifies the docstring to make it explicit. * Disambiguate `Instruction` #9666 (comment) --------- Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> (cherry picked from commit d6a8816)
* Improve docstring for `Statevector.evolve` I didn't realize from the generated documentation that `Statevector.evolve` can accept an `Instruction` or `QuantumCircuit`, not just an `Operator`. I only learned it once I found myself reading the source. This modifies the docstring to make it explicit. * Disambiguate `Instruction` #9666 (comment) --------- Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> (cherry picked from commit d6a8816) Co-authored-by: Jim Garrison <garrison@ibm.com>
* Improve docstring for `Statevector.evolve` I didn't realize from the generated documentation that `Statevector.evolve` can accept an `Instruction` or `QuantumCircuit`, not just an `Operator`. I only learned it once I found myself reading the source. This modifies the docstring to make it explicit. * Disambiguate `Instruction` Qiskit#9666 (comment) --------- Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Summary
I didn't realize from the generated documentation that
Statevector.evolve
can accept anInstruction
orQuantumCircuit
, not just anOperator
. I only learned it once I read the source. This modifies the docstring to make it explicit.Details and comments