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.