-
Notifications
You must be signed in to change notification settings - Fork 4
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
feat: QVM API module #289
feat: QVM API module #289
Conversation
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.
Overall LGTM 👍
Co-authored-by: jselig-rigetti <[email protected]>
Co-authored-by: jselig-rigetti <[email protected]>
multishot, expectation, and wavefunction requests as direct calls to the QVM API. The parameterized `run` and `run_program` functions have been lifted into the root of the QVM module.
names to a value describing whether to get all, none, or a specific list of indices for the address.
stubtest to default dev flow and resolve all stubtest issues
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.
Left some notes. A lot of comments were saved from when I started to review last week and might be outdated, though I tried to look for those.
Biggest thing is a spot where we are shifting elements in a Vec
a lot, with a suggestion on how to rewrite it.
I did not go through the Python/PyO3 stuff as carefully as I would have liked, but nothing stood out there.
QvmResponse into Result
allowing for easy parameterization of Programs before running on the QVM.
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.
A couple of suggestions and a question.
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.
Overall LGTM, a few nitpicks
Building up a QVM API that has feature parity with pyQuil's QVM client. This meant adding types and functions to support three additional request types. The
qvm::api
module contains all the types and functions to more or less directly interact with the QVM, while theqvm::run
andqvm::run_program
functions exist as a higher level means to support parameterized execution of a program on the QVM.I also fixed some issues with building the bindings as a Rust crate, added a stubtest task, and resolved all the existing stubtest issue.