Several algorithms are not applying FWD-ENV as they should #317

Activity

1. ericniebler

   added

   bugSomething isn't workingSomething isn't working

   P1

   on Jan 21, 2025
2. ericniebler

   added sub-issues on Jan 21, 2025

   • constraints on schedule_from's get-state function are incorrect #313
   • constraints on into_variant's get-state function are incorrect #314
   • when_all's receiver's environment is incorrectly forwarding all queries #315
   • let_value is not applying FWD-ENV as it should #316
   • stopped_as_optional tests constraints satisfaction of self instead of child #311
3. ericniebler

   added

   needs-proposed-resolutionThis issue does not yet have a proposed resolution but needs oneThis issue does not yet have a proposed resolution but needs one

   and removed

   needs-proposed-resolutionThis issue does not yet have a proposed resolution but needs oneThis issue does not yet have a proposed resolution but needs one

   on Jan 21, 2025
4. jwakely commented on Feb 3, 2025

   

   jwakely

   on Feb 3, 2025

   Member

   More actions

   I created https://cplusplus.github.io/LWG/issue4203 which should cover all of these
5. ericniebler

   added

   pending-wg21A paper or an LWG issue exitsA paper or an LWG issue exits

   on Feb 7, 2025
6. daniel-eiband-snkeos commented on Mar 19, 2025

   

   daniel-eiband-snkeos

   on Mar 19, 2025

   More actions

   Is as_awaitable another one such algorithm that doesn't handle forwarding correctly? See the use of env_of_t in awaitable-sender and in the definition of value-type of sender-awaitable. The environment of awaitable-receiver only forwards queries that satisfy forwarding-query.

   👍React with 👍1Reacted by Eric Niebler