Follow-up items from `dep-analysis` implementation
Open
Nobody has claimed this yet.
enhancement
stale-notified
- Dominant language
- C++
- Stars
- 1.1k
- Forks
- 456
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 165
Description
Required prerequisites
- Search the issue tracker to check if your feature has already been mentioned or rejected in other issues.
Describe the feature
In the interest of not holding up PR #2163, some open discussion items are being converted into an issue to track potential additional work items related to this pass.
- Reduce number of wires in default wire set: https://github.com/NVIDIA/cuda-quantum/pull/2163#discussion_r1739368793
- Add reset calls after every mz in order to comply with the pass assumptions listed in the pass description. Otherwise, our own tests are testing with undefined behavior. https://github.com/NVIDIA/cuda-quantum/pull/2163#discussion_r1739374979
- Update some of the dependency analysis tests to use pass statistics instead of return values. https://github.com/NVIDIA/cuda-quantum/pull/2163#discussion_r1739377897
- Make pass understand
quake.controltypes. https://github.com/NVIDIA/cuda-quantum/pull/2163#discussion_r1733500245 - Update tests to have non-constant
ifconditions: https://github.com/NVIDIA/cuda-quantum/pull/2163#discussion_r1739383192 - Fix memory leaks: https://github.com/NVIDIA/cuda-quantum/pull/2163#discussion_r1736832389
- TODO: If an unused wire flows through an
ifwith a useful wire ...: https://github.com/NVIDIA/cuda-quantum/pull/2163#discussion_r1736880288
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 with PR #2163, its dependency-analysis pass description, and the linked review discussions. The issue bundles seven separate items without naming files or defining a single completion target, so split one selected item into a focused issue with specific tests and a clear done condition before starting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100