Skip to content

Issues: cplusplus/sender-receiver

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clear current search query, filters, and sorts
41 Open 17 Closed
41 Open 17 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Figure out how/whether we should use P2830 "Standardized Constexpr Type Ordering" in sender/receiver design discussion We need to talk about this; there's nothing actionable here yet needs-paper Needs a paper to be written P0
#330 opened Feb 15, 2025 by lewissbaker
3
run_loop::run-loop-sender should remove the item from the list when a stop-request is sent design discussion We need to talk about this; there's nothing actionable here yet P0 processed processed in a meeting
#293 opened Oct 15, 2024 by lewissbaker
7
Does basic-receiver need to constrain set_value/set_error/set_stopped on whether complete is invocable? discussion We need to talk about this; there's nothing actionable here yet wording
#292 opened Oct 15, 2024 by lewissbaker
should queries be required to have a UUID so that there is a global canonical ordering? design discussion We need to talk about this; there's nothing actionable here yet needs-paper Needs a paper to be written P0
#289 opened Aug 28, 2024 by ericniebler
2
Should let_value destroy its predecessor operation-state eagerly to allow storage reuse? design discussion We need to talk about this; there's nothing actionable here yet P0
#287 opened Aug 14, 2024 by lewissbaker
2
Add support for strand-schedulers design discussion We need to talk about this; there's nothing actionable here yet enhancement New feature or request
#285 opened Aug 12, 2024 by lewissbaker
Should the default implementation of bulk support cancellation? design discussion We need to talk about this; there's nothing actionable here yet needs-paper Needs a paper to be written P0 Paper exists Paper exists, either WIP or pending-wg21 pending-wg21 A paper or an LWG issue exits processed processed in a meeting
#278 opened Jul 12, 2024 by lewissbaker
5
bulk does not specify what customizations need to do with exceptions thrown from invocations of f bug Something isn't working design discussion We need to talk about this; there's nothing actionable here yet P0 Paper exists Paper exists, either WIP or pending-wg21 pending-wg21 A paper or an LWG issue exits processed processed in a meeting
#276 opened Jul 12, 2024 by lewissbaker
4
Define a policy for resuming leaf operations that avoids running continuations inline on context that triggered completion async-scope Issues relating to the design of async_scope/counting_scope facilities. coroutines Issues relating to coroutine support. design discussion We need to talk about this; there's nothing actionable here yet needs-paper Needs a paper to be written P0
#269 opened Jul 4, 2024 by lewissbaker
5
is get_forward_progress_guarantee a forwarding query? discussion We need to talk about this; there's nothing actionable here yet P2
#207 opened Mar 19, 2024 by ericniebler
Integrate schedulers into the (synchronous) C++17 parallel algorithms discussion We need to talk about this; there's nothing actionable here yet enhancement New feature or request help wanted Extra attention is needed needs-paper Needs a paper to be written P1 tokyo Issues to be worked on in Tokyo 2024 workshop
#179 opened Jan 5, 2024 by ericniebler
@brycelelbach @rarutyun
integration of run_loop with other event loops discussion We need to talk about this; there's nothing actionable here yet enhancement New feature or request needs-paper Needs a paper to be written system-scheduler Tasks relating to the system-scheduler / thread-pool tokyo Issues to be worked on in Tokyo 2024 workshop
#172 opened Dec 29, 2023 by ericniebler
@maikel @kirkshoop
10
Do we still plan to integrate p2257's design for a blocking query? discussion We need to talk about this; there's nothing actionable here yet enhancement New feature or request P1 Paper exists Paper exists, either WIP or pending-wg21 tokyo Issues to be worked on in Tokyo 2024 workshop
#140 opened Dec 8, 2023 by ericniebler
@maikel
8
Feedback from Billy (split into multiple issues) discussion We need to talk about this; there's nothing actionable here yet enhancement New feature or request P0
#136 opened Dec 8, 2023 by ericniebler
4
recursion, inline completion, and stack usage discussion We need to talk about this; there's nothing actionable here yet enhancement New feature or request P0
#135 opened Dec 8, 2023 by ericniebler
2
Sending multiple values from then discussion We need to talk about this; there's nothing actionable here yet enhancement New feature or request needs-paper Needs a paper to be written P2
#133 opened Dec 8, 2023 by ericniebler
7
The specification of split should require that the input sender is only connected once. discussion We need to talk about this; there's nothing actionable here yet P0 wording
#129 opened Dec 8, 2023 by ericniebler
2
For the awaitable returned by as_awaitable, conditionally mark await_resume as [[noreturn]] discussion We need to talk about this; there's nothing actionable here yet enhancement New feature or request P2
#126 opened Dec 8, 2023 by ericniebler
consider rename execution::just discussion We need to talk about this; there's nothing actionable here yet naming
#122 opened Dec 8, 2023 by ericniebler
14
All executor facilities should be constexpr when possible discussion We need to talk about this; there's nothing actionable here yet P2
#119 opened Dec 8, 2023 by ericniebler
2
Should when_all[_with_variant] make any guarantees about completion context? discussion We need to talk about this; there's nothing actionable here yet enhancement New feature or request P2
#117 opened Dec 8, 2023 by ericniebler
1
error types should be nothrow-movable design discussion We need to talk about this; there's nothing actionable here yet P0 processed processed in a meeting
#115 opened Dec 8, 2023 by ericniebler
3
Avoiding inline execution in scoped algorithms discussion We need to talk about this; there's nothing actionable here yet
#111 opened Dec 8, 2023 by ericniebler
5
{#design-fpg} Questions about forward_progress_guarantee and get_forward_progress_guarantee() discussion We need to talk about this; there's nothing actionable here yet
#106 opened Dec 8, 2023 by ericniebler
6
[execution.senders.adaptors.bulk] Should clarify that bulk customisations are allowed to decay-copy 'args' if required bug Something isn't working design discussion We need to talk about this; there's nothing actionable here yet P0 Paper exists Paper exists, either WIP or pending-wg21 pending-wg21 A paper or an LWG issue exits processed processed in a meeting
#103 opened Dec 8, 2023 by ericniebler
4
ProTip! Find all open issues with in progress development work with linked:pr.