Unify PyQVM and QAM interfaces
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 358
- Avg merge
- 1d 58m
- Merged PRs (30d)
- 4
Description
I don't yet have an exhaustive list of the API differences, but one that immediately jumped out at me is the absence of a run_and_measure method on the PyQVM. Furthermore, calling run returns a PyQVM rather than a list of bitstrings.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the public PyQVM and QAM interfaces, focusing on the reported run_and_measure absence and the return value of run. Done means the relevant interface differences are identified and the two behaviors are made consistent, with coverage for these calls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- quantum-computing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100