Skip to content
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

Merged
merged 46 commits into from
Jun 2, 2023

Conversation

MarquessV
Copy link
Contributor

@MarquessV MarquessV commented May 2, 2023

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 the qvm::run and qvm::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.

@MarquessV MarquessV changed the title create qvm::api submodule feat: QVM API module May 3, 2023
@MarquessV MarquessV marked this pull request as ready for review May 3, 2023 17:59
Copy link
Contributor

@jselig-rigetti jselig-rigetti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall LGTM 👍

MarquessV and others added 12 commits May 3, 2023 14:02
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.
@MarquessV MarquessV requested a review from jselig-rigetti May 22, 2023 22:32
Copy link
Contributor

@Shadow53 Shadow53 left a 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.

Copy link
Contributor

@Shadow53 Shadow53 left a 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.

@MarquessV MarquessV requested a review from Shadow53 May 30, 2023 20:06
Copy link
Contributor

@jselig-rigetti jselig-rigetti left a 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

@MarquessV MarquessV merged commit 1d35b15 into main Jun 2, 2023
@MarquessV MarquessV deleted the 288-expose-functions-to-interact-with-qvm-directly branch June 2, 2023 17:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants