Skip to content

Commit 0d32d6d

Browse files
committed
New issue from Dietmar Kühl: affine_on semantics
1 parent a0633ca commit 0d32d6d

File tree

1 file changed

+15
-0
lines changed

1 file changed

+15
-0
lines changed

xml/issue4330.xml

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,21 @@
1010

1111
<discussion>
1212
<p>
13+
The specification of <code>affine_on</code> uses "current execution
14+
resource" and it is unclear what that means exactly. Additionally,
15+
it is unclear what the difference between <code>affine_on</code>
16+
and <code>continues_on</code> is. The intended difference for
17+
<code>affine_on</code> is to avoid unnecessary scheduling which
18+
<code>continues_on</code> is already allowed to do in some cases,
19+
too.
20+
</p>
21+
<p>
22+
The intended semantics is that <code>affine_on</code> will either
23+
complete inline on whatever execution agent it was started on or
24+
it will complete asynchronously on the specified execution context.
25+
With this formulation <code>affine_on</code> may complete on one
26+
of two different execution context if it is started on an execution
27+
context that is different from the one specified by the scheduler.
1328
</p>
1429
</discussion>
1530

0 commit comments

Comments
 (0)