Issues

`run_loop` should not have a `set_error` completion signature

cplusplus/sender-receiver#351 · opened

on Nov 16, 2025

remove test for `get_env` `noexcept`-ness from `inline_scheduler`

cplusplus/sender-receiver#349 · opened

on Nov 5, 2025

1

`let_value/error/stopped` should specify the attributes of their senders

cplusplus/sender-receiver#346 · opened

on Oct 16, 2025

1

`check-values` function for `upon_error` and `upon_stopped` is wrong

cplusplus/sender-receiver#344 · opened

on Aug 31, 2025

potential dangling reference returned from `transform_sender`

cplusplus/sender-receiver#343 · opened

on Aug 30, 2025

1

`on(sch,sndr)` should specify its attributes

cplusplus/sender-receiver#341 · opened

on Jun 22, 2025

`scheduler` concept is missing a requirement regarding domains

cplusplus/sender-receiver#338 · opened

on May 31, 2025

troubles with the customizations of `continues_on` and `schedule_from`

cplusplus/sender-receiver#337 · opened

on May 19, 2025

`transform_env` should take the sender by lvalue reference

cplusplus/sender-receiver#336 · opened

on May 19, 2025

"inline" sender adaptors should forward the `get_forward_progress_guarantee` query

cplusplus/sender-receiver#334 · opened

on May 16, 2025

1

query objects must be default constructible

cplusplus/sender-receiver#333 · opened

on May 5, 2025

potentially throwing `run_loop::finish` can cause `sync_wait` to call `terminate` or hang

cplusplus/sender-receiver#329 · opened

on Feb 13, 2025

1

define an execution environment's salient properties

cplusplus/sender-receiver#328 · opened

on Feb 11, 2025

1

[exec.connect] wording needs to ensure that in `connect(sndr, rcvr)` that `rcvr` expression is only evaluated once

cplusplus/sender-receiver#325 · opened

on Feb 5, 2025

2

[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()

cplusplus/sender-receiver#324 · opened

on Feb 4, 2025

Should `set_value/error/stopped` CPOs require that member-functions return `void`?

cplusplus/sender-receiver#323 · opened

on Feb 4, 2025

2

alias template `connect_result_t` should be constrained with `sender_to`

cplusplus/sender-receiver#320 · opened

on Feb 2, 2025

3

`let_[].transform_env` is specified in terms of the `let_` sender itself instead of its child

cplusplus/sender-receiver#319 · opened

on Feb 2, 2025

1

specification of `as-sndr2(Sig)` in [exec.let] is incomplete

cplusplus/sender-receiver#318 · opened

on Feb 2, 2025

1

Several algorithms are not applying `FWD-ENV` as they should

cplusplus/sender-receiver#317 · opened

on Jan 21, 2025

2

`let_value` is not applying `FWD-ENV` as it should

cplusplus/sender-receiver#316 · opened

on Jan 21, 2025

`when_all`'s receiver's environment is incorrectly forwarding all queries

cplusplus/sender-receiver#315 · opened

on Jan 21, 2025

constraints on `into_variant`'s `get-state` function are incorrect

cplusplus/sender-receiver#314 · opened

on Jan 20, 2025

constraints on `schedule_from`'s `get-state` function are incorrect

cplusplus/sender-receiver#313 · opened

on Jan 19, 2025

The `operation_state` concept can be simplified

cplusplus/sender-receiver#312 · opened

on Jan 14, 2025

1

Navigation Menu

Repository navigation

Issues

`run_loop` should not have a `set_error` completion signature

remove test for `get_env` `noexcept`-ness from `inline_scheduler`

`let_value/error/stopped` should specify the attributes of their senders

`check-values` function for `upon_error` and `upon_stopped` is wrong

potential dangling reference returned from `transform_sender`

`on(sch,sndr)` should specify its attributes

`scheduler` concept is missing a requirement regarding domains

troubles with the customizations of `continues_on` and `schedule_from`

`transform_env` should take the sender by lvalue reference

"inline" sender adaptors should forward the `get_forward_progress_guarantee` query

query objects must be default constructible

potentially throwing `run_loop::finish` can cause `sync_wait` to call `terminate` or hang

define an execution environment's salient properties

[exec.connect] wording needs to ensure that in `connect(sndr, rcvr)` that `rcvr` expression is only evaluated once

[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()

Should `set_value/error/stopped` CPOs require that member-functions return `void`?

alias template `connect_result_t` should be constrained with `sender_to`

`let_[].transform_env` is specified in terms of the `let_` sender itself instead of its child

specification of `as-sndr2(Sig)` in [exec.let] is incomplete

Several algorithms are not applying `FWD-ENV` as they should

`let_value` is not applying `FWD-ENV` as it should

`when_all`'s receiver's environment is incorrectly forwarding all queries

constraints on `into_variant`'s `get-state` function are incorrect

constraints on `schedule_from`'s `get-state` function are incorrect

The `operation_state` concept can be simplified