Issues

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

cplusplus/sender-receiver#349 · opened

on Nov 5, 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

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

`stopped_as_optional` tests constraints satisfaction of self instead of child

cplusplus/sender-receiver#311 · opened

on Jan 14, 2025

`with-await-transform::await_transform` should not use a deduced return type

cplusplus/sender-receiver#309 · opened

on Jan 7, 2025

2

constraints on user customizations of standard sender algorithms are incorrectly specified

cplusplus/sender-receiver#308 · opened

on Jan 2, 2025

2

specification of `completion-signatures-for` in [exec.snd.expos]/p39 is recursive

cplusplus/sender-receiver#307 · opened

on Dec 31, 2024

2

restore the `enable_sender` boolean variable template

cplusplus/sender-receiver#306 · opened

on Dec 5, 2024

1

`schedule_from` isn't starting the schedule sender if decay-copying results throws

cplusplus/sender-receiver#304 · opened

on Nov 21, 2024

2

`get_env()` specified in terms of `as_const()` but this doesn't work with rvalue senders

cplusplus/sender-receiver#296 · opened

on Oct 22, 2024

3

Should the default implementation of `bulk` support cancellation?

cplusplus/sender-receiver#278 · opened

on Jul 12, 2024

5

`bulk` doesn't explicitly grant permissions for customisations to execute `f` concurrently

cplusplus/sender-receiver#277 · opened

on Jul 12, 2024

1

`bulk` does not specify what customizations need to do with exceptions thrown from invocations of `f`

cplusplus/sender-receiver#276 · opened

on Jul 12, 2024

4

bulk doesn't give the caller a way to constrain how function can be executed

cplusplus/sender-receiver#275 · opened

on Jul 12, 2024

4

The use of `JOIN-ENV` leads to inefficient implementations of composed environments

cplusplus/sender-receiver#229 · opened

on May 20, 2024

2

Should the `receiver` concept require that move-construction is nothrow?

cplusplus/sender-receiver#226 · opened

on May 16, 2024

2

[exec.when.all] Wording of `impls-for<when_all_t>::get-env` results in inefficient implementations of `get_env()`

cplusplus/sender-receiver#199 · opened

on Feb 22, 2024

1

Navigation Menu

Repository navigation

Issues

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

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

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

`stopped_as_optional` tests constraints satisfaction of self instead of child

`with-await-transform::await_transform` should not use a deduced return type

constraints on user customizations of standard sender algorithms are incorrectly specified

specification of `completion-signatures-for` in [exec.snd.expos]/p39 is recursive

restore the `enable_sender` boolean variable template

`schedule_from` isn't starting the schedule sender if decay-copying results throws

`get_env()` specified in terms of `as_const()` but this doesn't work with rvalue senders

Should the default implementation of `bulk` support cancellation?

`bulk` doesn't explicitly grant permissions for customisations to execute `f` concurrently

`bulk` does not specify what customizations need to do with exceptions thrown from invocations of `f`

bulk doesn't give the caller a way to constrain how function can be executed

The use of `JOIN-ENV` leads to inefficient implementations of composed environments

Should the `receiver` concept require that move-construction is nothrow?

[exec.when.all] Wording of `impls-for<when_all_t>::get-env` results in inefficient implementations of `get_env()`