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

Implement sequence sender algorithms

Open
#943 0 comments 2 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
Domain
tooling

Research direction

Start by reviewing the existing contents of exec/ and the sequence sender APIs. The issue lists many unchecked sources, sinks, adaptors, and queries but names no specific entry point or tests, so select and scope one algorithm before implementation. Done is not defined for the full checklist.

Written by the indexing model from the issue text.

Description

Here is a list of sequence sender algorithms and types that could be included into exec/

Types

  • any_sequence_of

Sinks

  • ignore_all(sequence) -> sender
    Returns a sender that completes when the input sequence completes. If an element of the sequence completes with an set_error_t(E) or set_stopped_t() a stop request will be issued and the signal will be forwarded.
  • first_value(sequence) -> sender
  • last_value(sequence) -> sender
  • reduce

Sources

  • empty_sequence() -> sequence
  • sender -> sequence
  • repeat(sender) -> sequence
  • generate_each(fn) -> sequence
  • iterate(range) -> sequence

Adaptors

  • merge_all(sequences, ...) -> sequence, merge_all_sequence(sequence) -> sequence
  • filter_each(sequence, predicate) -> sequence
  • take_while(sequence, predicate) -> sequence
  • transform_each(sequence, adaptor) -> sequence
  • zip(sequences, ...) -> sequence
  • scan

Queries

  • capacity (?)
  • parallelism (?)
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.