Skip to content

Commit 22777c2

Browse files
authored
New issue from Dietmar: Affine on semantics
1 parent ecf3017 commit 22777c2

File tree

1 file changed

+36
-0
lines changed

1 file changed

+36
-0
lines changed

xml/issue4330.xml

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
<?xml version='1.0' encoding='utf-8' standalone='no'?>
2+
<!DOCTYPE issue SYSTEM "lwg-issue.dtd">
3+
4+
<issue num="4330" status="New">
5+
<title><code>affine_on</code> semantics</title>
6+
<section><sref ref="[exec.affine.on]"/></section>
7+
<submitter>Dietmar Kühl</submitter>
8+
<date>31 Aug 2025</date>
9+
<priority>99</priority>
10+
11+
<discussion>
12+
<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.
28+
</p>
29+
</discussion>
30+
31+
<resolution>
32+
<p>
33+
</p>
34+
</resolution>
35+
36+
</issue>

0 commit comments

Comments
 (0)