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

implement `fork( closure0, closure1,... )` and `select<1,2,3>()` adaptors

Open
#940 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp

Research direction

The issue names no implementation files or tests. Start by reviewing existing adaptor entry points and the semantics of split, let_value, and when_all; done means fork, pass_through, and select<I,J,K> support the shown composition with matching tests.

Written by the indexing model from the issue text.

Description

enhancement P2
snd | fork( closure0, closure1 )

would be like:

just(split(snd)) 
  | let_value([](auto snd) {
      return when_all(snd | closure0, snd | closure1);
    })

It could be useful in tandem with a no-op pass_through adaptor and a select<I,J,K> adaptor that forwards only the I-th, J-th, K-th value. Then we could do something like:

snd | fork( pass_through, select<1,2,3> | then(f) )
Dominant language
C++
Stars
2.4k
Forks
270
Avg merge
2d 17h
Merged PRs (30d)
37

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.