Make QuilAtom/AbstractInstruction objects immutable
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 358
- Avg merge
- 1d 58m
- Merged PRs (30d)
- 4
Description
you can run into lots of weird edge cases if you are allowed to modify these. Particularly if they're included by reference in multiple places
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 locating the definitions and usages of QuilAtom and AbstractInstruction, then inspect how these objects are shared by reference. Determine which mutation paths need to be prevented and review existing tests around these classes. Done means the objects cannot be modified after creation without breaking the library's expected behavior, with regression coverage for shared references.
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
- 35/100