Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

`just` senders are move/copy constructible but not assignable

Open
#1,159 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
backend

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.

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?

Dominant language
C++
Stars
2.4k
Forks
270
Avg merge
2d 16h
Merged PRs (30d)
43

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NVIDIA/stdexec

All issues in NVIDIA/stdexec

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.