-
Notifications
You must be signed in to change notification settings - Fork 4
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.
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
Author
Label
Projects
Milestones
Assignee
Sort
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
potentially throwing Something isn't working
P0
wording
run_loop::finish
can cause sync_wait
to call terminate
or hang
bug
#329
opened Feb 13, 2025 by
ericniebler
define an execution environment's salient properties
bug
Something isn't working
P1
#328
opened Feb 11, 2025 by
ericniebler
[exec.snd.concepts] Needs a paper to be written
P0
sender_to
concept should avoid checking that the receiver's completion-methods are present
design
needs-paper
#327
opened Feb 8, 2025 by
lewissbaker
[exec.connect] wording needs to ensure that in Something isn't working
P2
pending-wg21
A paper or an LWG issue exits
wording
connect(sndr, rcvr)
that rcvr
expression is only evaluated once
bug
#325
opened Feb 5, 2025 by
lewissbaker
[exec.snd.expos] Not clear if get-domain-late should evaluate the get_domain() expression or default-construct a domain of the type returned by get_domain()
bug
Something isn't working
wording
#324
opened Feb 4, 2025 by
lewissbaker
Should Something isn't working
design
P0
set_value/error/stopped
CPOs require that member-functions return void
?
bug
#323
opened Feb 4, 2025 by
lewissbaker
receiver/sender constraint that checks New feature or request
wording
get_env(rcvr)
is valid redundantly checks the result is queryable
editorial
enhancement
#322
opened Feb 3, 2025 by
lewissbaker
receiver/sender concepts require New feature or request
wording
get_env
but this has a fallback that accepts any type
enhancement
#321
opened Feb 3, 2025 by
lewissbaker
alias template Something isn't working
P1
pending-wg21
A paper or an LWG issue exits
connect_result_t
should be constrained with sender_to
bug
#320
opened Feb 2, 2025 by
ericniebler
let_[*].transform_env
is specified in terms of the let_*
sender itself instead of its child
bug
#319
opened Feb 2, 2025 by
ericniebler
specification of Something isn't working
P1
pending-wg21
A paper or an LWG issue exits
as-sndr2(Sig)
in [exec.let] is incomplete
bug
#318
opened Feb 2, 2025 by
ericniebler
Several algorithms are not applying Something isn't working
P1
pending-wg21
A paper or an LWG issue exits
FWD-ENV
as they should
bug
#317
opened Jan 21, 2025 by
ericniebler
let_value
is not applying FWD-ENV
as it should
bug
#316
opened Jan 21, 2025 by
ericniebler
when_all
's receiver's environment is incorrectly forwarding all queries
bug
#315
opened Jan 21, 2025 by
ericniebler
constraints on Something isn't working
P1
pending-wg21
A paper or an LWG issue exits
into_variant
's get-state
function are incorrect
bug
#314
opened Jan 20, 2025 by
ericniebler
constraints on Something isn't working
P1
pending-wg21
A paper or an LWG issue exits
schedule_from
's get-state
function are incorrect
bug
#313
opened Jan 19, 2025 by
ericniebler
The Something isn't working
P2
pending-wg21
A paper or an LWG issue exits
operation_state
concept can be simplified
bug
#312
opened Jan 14, 2025 by
ericniebler
stopped_as_optional
tests constraints satisfaction of self instead of child
bug
#311
opened Jan 14, 2025 by
ericniebler
with-await-transform::await_transform
should not use a deduced return type
bug
#309
opened Jan 7, 2025 by
t3nsor
constraints on user customizations of standard sender algorithms are incorrectly specified
bug
Something isn't working
needs-proposed-resolution
This issue does not yet have a proposed resolution but needs one
P1
pending-wg21
A paper or an LWG issue exits
#308
opened Jan 2, 2025 by
ericniebler
specification of Something isn't working
P0
pending-wg21
A paper or an LWG issue exits
completion-signatures-for
in [exec.snd.expos]/p39 is recursive
bug
#307
opened Dec 31, 2024 by
ericniebler
restore the Something isn't working
P0
pending-wg21
A paper or an LWG issue exits
enable_sender
boolean variable template
bug
#306
opened Dec 5, 2024 by
ericniebler
schedule_from
isn't starting the schedule sender if decay-copying results throws
bug
#304
opened Nov 21, 2024 by
ericniebler
Add execution::invoke() algorithm
enhancement
New feature or request
good-first-issue
Something to try if you're new to the project
needs-paper
Needs a paper to be written
P1
#303
opened Nov 18, 2024 by
lewissbaker
Previous Next
ProTip!
no:milestone will show everything without a milestone.