Revisit how we update from CCCL v2.x to v3.x
Open
Nobody has claimed this yet.
stale-notified
- Dominant language
- C++
- Stars
- 1.1k
- Forks
- 456
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 165
Description
Required prerequisites
- Consult the security policy. If reporting a security vulnerability, do not report the bug using this form. Use the process described in the policy to report the issue.
- Make sure you've read the documentation. Your issue may be addressed there.
- Search the issue tracker to verify that this hasn't already been reported. +1 or comment there if it has.
- If possible, make a PR with a failing test to give us a starting point to work on!
Describe the bug
Compiler flags were added to remove an ambiguous error https://github.com/NVIDIA/cuda-quantum/commit/1934d3af7e9b2fb2bffa228d156f4b9b9b4a61df
This should be handled better without compiler flags.
Steps to reproduce the bug
N/A
Expected behavior
N/A
Is this a regression? If it is, put the last known working version (or commit) here.
Not a regression
Environment
N/A
Suggestions
No response
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 reviewing commit 1934d3af7e9b2fb2bffa228d156f4b9b9b4a61df and the compiler flags it introduced for the CCCL update. Determine how the ambiguous error should be handled without those flags, then add a failing test or other reproducible coverage showing the intended behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system, compilers
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100