`nvexec::let_value` and friends don't appear to be persisting the function args
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.4k
- Forks
- 270
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 39
Description
The arguments to let_value's callable should be persisted for the duration of the successor operation. Here, it looks like the arguments are discarded after the callable returns the successor sender.
@senior-zero is there a reason why keeping the arguments around like stdexec::let_value does would be problematic for the CUDA stream scheduler?
Contributor guide
No contributing guide indexed for this repository
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 include/nvexec/stream/let_xxx.cuh around lines 117-118 and compare the lifetime handling with stdexec::let_value. Trace the successor operation to confirm whether the callable's arguments are discarded too early; done means the arguments remain available for the successor operation without breaking the CUDA stream scheduler.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100