Properly fill (read-only) declared memory regions on QPU
Open
Nobody has claimed this yet.
help wanted :wave:
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 358
- Avg merge
- 1d 58m
- Merged PRs (30d)
- 4
Description
The QPU is restricted to writing to the "ro" memory region. Writing (via MEASURE) to any other memory raises an error. You can, however, declare a memory region and this memory region should be populated in QPU._memory_results for parity with QVM behaviour.
See #873, #981, and #982.
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 at QPU._memory_results and compare how declared memory regions are populated by QVM. Trace the MEASURE handling and the restriction to the "ro" region, using #873, #981, and #982 for context. Done means declared read-only regions are populated on QPU with behavior matching QVM.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- quantum-computing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100