Skip to content

Commit b1f783a

Browse files
committed
Set 4354 to P3 and send to SG1 and LEWG
1 parent e8acf5e commit b1f783a

File tree

1 file changed

+33
-2
lines changed

1 file changed

+33
-2
lines changed

xml/issue4354.xml

Lines changed: 33 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
<?xml version='1.0' encoding='utf-8' standalone='no'?>
22
<!DOCTYPE issue SYSTEM "lwg-issue.dtd">
33

4-
<issue num="4354" status="New">
4+
<issue num="4354" status="SG1">
55
<title>Reconsider `weakly_parallel` as the default `forward_progress_guarantee`</title>
66
<section>
77
<sref ref="[exec.get.fwd.progress]"/>
88
</section>
99
<submitter>Lewis Baker</submitter>
1010
<date>25 Aug 2025</date>
11-
<priority>99</priority>
11+
<priority>3</priority>
1212

1313
<discussion>
1414
<p>
@@ -45,6 +45,37 @@ implementations to be much more aware of the fact that these are the guarantees
4545
thus could be more expected to customize the `get_forward_progress_guarantee` query to return the
4646
respective values.
4747
</p>
48+
49+
<note>2025-10-20; Reflector poll. Status changed: New &rarr; SG1</note>
50+
<p>
51+
Set priority to 3 after reflector poll. Send to SG1 and LEWG.
52+
</p>
53+
<p>
54+
"If there is a default, it should be the weakest possible one.
55+
If that is an unfortunate choice I’d rather prefer no default and mandate
56+
that the query gets implemented. Providing a default which is stronger than
57+
the weakest possible creates logic errors. Accidentally claiming weaker
58+
than the actual value is only a performance error."
59+
</p>
60+
<p>
61+
"This is tension between the default being promising the least and
62+
the default being the most likely thing a user wants to do.
63+
Assuming the least powerful guarantees unless the user has opted in is safer.
64+
Changing this choice requires going back to LEWG or SG1."
65+
</p>
66+
<p>
67+
"Plenty of reasonable schedulers are weakly parallel at best.
68+
It's the right default. If your scheduler offers better than
69+
that, you would naturally remember to customize it."
70+
</p>
71+
<p>
72+
"It seems that the authors of `run_loop::scheduler` did not naturally remember to customize it.
73+
It's possible the intent was that `run_loop::scheduler` should not offer better
74+
than `weakly_parallel` forward progress, but it was not discussed in P2300.
75+
The absence of an explicit implementation of the query could either be
76+
intentional or an accidental omission.
77+
Perhaps this is an indication that there should not be a default forward-progress guarantee for schedulers?"
78+
</p>
4879
</discussion>
4980

5081
<resolution>

0 commit comments

Comments
 (0)