`just` senders are move/copy constructible but not assignable
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.4k
- Forks
- 270
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 39
Description
See https://godbolt.org/z/GW7cfea31 for a reproducer. I would expect them to be assignable if they're copy/move constructible. The source seems to be __make_tuple (https://github.com/NVIDIA/stdexec/blob/869fb2a7767d30bff486b589533b0346e4dd5454/include/stdexec/__detail/__basic_sender.hpp#L612-L653) which is a lambda with captures, which makes the just sender non-assignable. Is this expected or intentional? Does __make_tuple need to be implemented that way?
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 with the Godbolt reproducer, then inspect __make_tuple in include/stdexec/__detail/__basic_sender.hpp at lines 612-653. Determine whether the observed non-assignability of just senders is intentional or should change, and document or validate the expected behavior with a focused test.
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