- Title
- affine_on semantics
- Status
- lewg
- Section
- [exec.affine.on]
- Submitter
- Dietmar Kühl
Created on 2025-08-31.00:00:00 last changed 3 weeks ago
Messages
[ 2025-10-24; Resolves US 233-365 ]
[ 2025-10-23; Reflector poll. Status changed: New → LEWG ]
Set priority to 2 after reflector poll. Send to LEWG.
The specification of affine_on uses "current execution
resource" and it is unclear what that means exactly. Additionally,
it is unclear what the difference between affine_on
and continues_on is. The intended difference for
affine_on is to avoid unnecessary scheduling which
continues_on is already allowed to do in some cases,
too.
The intended semantics is that affine_on will either
complete inline on whatever execution agent it was started on or
it will complete asynchronously on the specified execution context.
With this formulation affine_on may complete on one
of two different execution context if it is started on an execution
context that is different from the one specified by the scheduler.
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2025-10-27 09:58:11 | admin | set | messages: + msg15438 |
| 2025-10-23 11:05:16 | admin | set | messages: + msg15378 |
| 2025-10-23 11:05:16 | admin | set | status: new -> lewg |
| 2025-08-31 00:00:00 | admin | create | |