PennyLaneAI / PennyLaneAI/catalyst
3029 follow-up: Update device capabilities for dynamic allocation
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 234
- Forks
- 84
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 66
Description
Commenting here to open an issue:
We should update devices to properly declare whether they support dynamic allocation or not. Both null.qubit and lightning.qubit should support it. Then the TODO and capability override can be removed.
Originally posted by @dime10 in https://github.com/PennyLaneAI/catalyst/pull/3029#discussion_r3639244375
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
Locate the device capability declarations for null.qubit and lightning.qubit, then trace the TODO and capability override mentioned in the issue. Update both devices to declare dynamic-allocation support and confirm the obsolete TODO and override are removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100