-
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
schedule_from
isn't starting the schedule sender if decay-copying results throws
#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
P1
#303
opened Nov 18, 2024 by
lewissbaker
Relax when_all to allow other stop-token implementations than inplace_stop_token
design
discussion
We need to talk about this; there's nothing actionable here yet
P0
#302
opened Nov 7, 2024 by
lewissbaker
sync_wait
should work with just_stopped()
and just_error(e)
.
#299
opened Oct 22, 2024 by
BenFrantzDale
when_all
should be described explicitly as not intrinsically parallel
#298
opened Oct 22, 2024 by
BenFrantzDale
when_all(just())
shouldn’t have a set_stopped_t()
completion signature
design
needs-paper
#297
opened Oct 22, 2024 by
BenFrantzDale
get_env()
specified in terms of as_const()
but this doesn't work with rvalue senders
bug
#296
opened Oct 22, 2024 by
lewissbaker
Should
when_all
and split
check the receiver's stop token for stop_requested()
and call set_stopped
?
#295
opened Oct 18, 2024 by
jiixyj
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
Does We need to talk about this; there's nothing actionable here yet
wording
basic-receiver
need to constrain set_value/set_error/set_stopped
on whether complete
is invocable?
discussion
#292
opened Oct 15, 2024 by
lewissbaker
env
and prop
are relying on deprecated behavior
bug
#291
opened Oct 14, 2024 by
ericniebler
execution::split: Conflict between shared_state<Child_Sndr> and shared_state<Out_Sndr>
#290
opened Oct 4, 2024 by
mochunshuang
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
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
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
Clarify the semantics/requirements of the get_scheduler query
bug
Something isn't working
design
P0
#284
opened Aug 3, 2024 by
lewissbaker
Definition of Something isn't working
design
P0
SCHED-ATTRS
incorrectly assumes that schedule operations that complete with set_stopped will complete on that scheduler
bug
#283
opened Aug 1, 2024 by
lewissbaker
grant
connect
permission to return a type other than decltype(sndr.connect(rcvr))
design
P0
#281
opened Jul 19, 2024 by
ericniebler
Should the default implementation of 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
bulk
support cancellation?
design
discussion
#278
opened Jul 12, 2024 by
lewissbaker
bulk
doesn't explicitly grant permissions for customisations to execute f
concurrently
bug
#277
opened Jul 12, 2024 by
lewissbaker
bulk
does not specify what customizations need to do with exceptions thrown from invocations of f
bug
#276
opened Jul 12, 2024 by
lewissbaker
Previous Next
ProTip!
Follow long discussions with comments:>50.