Skip to content

Commit fffae08

Browse files
jwakelyjwakely
committed
Set priorities based on reflector polls
1 parent 89ee742 commit fffae08

File tree

7 files changed

+94
-7
lines changed

7 files changed

+94
-7
lines changed

‎xml/issue4116.xml‎

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,13 +7,21 @@
77
<section><sref ref="[range.enumerate.iterator]"/><sref ref="[range.cartesian.iterator]"/></section>
88
<submitter>Hewill Kang</submitter>
99
<date>07 Jul 2024</date>
10-
<priority>99</priority>
10+
<priority>3</priority>
1111

1212
<discussion>
1313
<p>
1414
These two iterators do not support <tt>*r++</tt> for non-forward iterators,
1515
so we should not provide <tt>iterator_category</tt> as they are not C++17 iterators.
1616
</p>
17+
18+
<note>2025-10-21; Reflector poll.</note>
19+
<p>
20+
Set priority to 3 after reflector poll.
21+
</p>
22+
<p>
23+
Six votes for Tentatively Ready, but not unanimous.
24+
</p>
1725
</discussion>
1826

1927
<resolution>

‎xml/issue4211.xml‎

Lines changed: 23 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
</section>
99
<submitter>Jonathan Wakely</submitter>
1010
<date>22 Feb 2025</date>
11-
<priority>99</priority>
11+
<priority>2</priority>
1212

1313
<discussion>
1414
<p>
@@ -45,6 +45,28 @@ The standard could be adjusted to support chains of links by allowing
4545
algorithm used by `tzdb::locate_zone(string_view)` to find a `time_zone` from
4646
a name that might be a zone or a link.
4747
</p>
48+
49+
<note>2025-10-21; Reflector poll.</note>
50+
<p>
51+
Set priority to 2 after reflector poll.
52+
Add Jonathan's comments on the resolution:
53+
</p>
54+
<p>
55+
The goal of the resolution is to permit `time_zone_link::target` to name
56+
another link, and not overspecify `tzdb::locate_zone` to require that
57+
`tz_l.target()` names a valid zone `tz`. Considered normatively saying what
58+
happens if a link chain doesn't terminate in a zone (like the zic(8) man page
59+
does), but that seemed like overspecification. We don't currently say what
60+
happens if a non-chained link has an invalid target, it's just covered by
61+
`locate_zone` failing to find anything.
62+
So just added a note saying bad chains are bad.
63+
</p>
64+
<p>
65+
Not urgent, as Libstdc++ and libc++ already handle this in some form.
66+
Links that use the same name as zones are unlikely to be a problem with the
67+
official IANA database, probably only relevant for manually edited data.
68+
Likewise for cycles in link chains. Maybe just leave to QoI.
69+
</p>
4870
</discussion>
4971

5072
<resolution>

‎xml/issue4214.xml‎

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
</section>
99
<submitter>Hewill Kang</submitter>
1010
<date>15 Feb 2025</date>
11-
<priority>99</priority>
11+
<priority>3</priority>
1212

1313
<discussion>
1414
<p>
@@ -88,6 +88,16 @@ and <code>F</code> are indeterminately sequenced.
8888
Upon reflector discussion many preferred to use instead the new <i>Hardened preconditions:</i> element which
8989
have been introduced by the recently voted in <paper num="P3471R4"/>.
9090
</p>
91+
92+
<note>2025-10-21; Reflector poll.</note>
93+
<p>
94+
Set priority to 3 after reflector poll.
95+
</p>
96+
<p>
97+
"Disagreement on whether to introduce <i>Hardened preconditions</i> in this Clause.
98+
Some discomfort with adding the element as a bullet point inside a list,
99+
no better suggestions though.
100+
</p>
91101
</discussion>
92102

93103
<resolution>

‎xml/issue4219.xml‎

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

4-
<issue num="4219" status="New">
4+
<issue num="4219" status="Tentatively NAD">
55
<title><tt>std::vector::erase[_if]</tt> should be based on ranges `remove`</title>
66
<section>
77
<sref ref="[vector.erasure]"/>
@@ -27,6 +27,17 @@ other non-ranges algorithms that take predicates should be updated to use invoke
2727
If that's true, though, it's perplexing why a new-to-c++20 function like `std::vector::erase_if`
2828
should suffer the same drawback.
2929
</p>
30+
31+
<note>2025-10-21; Reflector poll. Status changed: New &rarr; Tentatively NAD.</note>
32+
<p>
33+
"This is a design change and needs a paper."
34+
</p>
35+
36+
<note>2025-10-21; .</note>
37+
<p>
38+
"Paper should discuss whether <code>std::erase_if(c, &amp;T::mf)</code> works on paper,
39+
currently works on STL implementations in the field, and whether it <i>should</i> work."
40+
</p>
3041
</discussion>
3142

3243
<resolution>

‎xml/issue4249.xml‎

Lines changed: 17 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
</section>
99
<submitter>Hewill Kang</submitter>
1010
<date>26 Apr 2025</date>
11-
<priority>99</priority>
11+
<priority>2</priority>
1212

1313
<discussion>
1414
<p>
@@ -68,6 +68,22 @@ when `_ITERATOR_DEBUG_LEVEL` is turned on.
6868
It seems that extra flags are needed to fix this issue because `output_it` should not
6969
be considered to reach the end when we back to the outer loop.
7070
</p>
71+
72+
<note>2025-10-21; Reflector poll.</note>
73+
<p>
74+
Set priority to 2 after reflector poll.
75+
</p>
76+
<p>
77+
"This is unfortunate. `lazy_split` is probably not very commonly used,
78+
but handling input ranges was half the reason why we kept it around.
79+
Can we reuse `trailing_empty_` for this instead of adding a new flag?
80+
Both flags have the same meaning, and the two cases where they are true
81+
are disjoint: we need `has_next_` when iterating through the inner range
82+
exhausted the source range; we need `trailing_empty_` when we find a delimiter
83+
at the end of the source range when incrementing the outer iterator,
84+
which by definition means that iterating through the inner range
85+
<i>didn't</i> exhaust it."
86+
</p>
7187
</discussion>
7288

7389
<resolution>

‎xml/issue4254.xml‎

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@
66
<section><sref ref="[range.stride.iterator]"/></section>
77
<submitter>Hewill Kang</submitter>
88
<date>01 May 2025</date>
9-
<priority>99</priority>
9+
<priority>3</priority>
1010

1111
<discussion>
1212
<p>
@@ -21,6 +21,11 @@ It turns out this is also true for <code>stride_view::<i>iterator</i></code>, su
2121
There is no reason to give up this convenience because <code>stride_view::<i>iterator</i></code> is intended
2222
to preserve the nature of the underlying iterator.
2323
</p>
24+
25+
<note>2025-10-21; Reflector poll.</note>
26+
<p>
27+
Set priority to 3 after reflector poll.
28+
</p>
2429
</discussion>
2530

2631
<resolution>

‎xml/issue4364.xml‎

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
</section>
99
<submitter>Jiang An</submitter>
1010
<date>05 Sep 2025</date>
11-
<priority>99</priority>
11+
<priority>4</priority>
1212

1313
<discussion>
1414
<p>
@@ -35,6 +35,21 @@ require them to be SFINAE-friendly to reduce potential conflicts with user-provi
3535
<p/>
3636
If it's intended to allow implementation divergence, perhaps we should clarify the intent.
3737
</p>
38+
39+
<note>2025-10-21; Reflector poll.</note>
40+
<p>
41+
Set priority to 4 after reflector poll.
42+
</p>
43+
<p>
44+
"Does it matter in practice? If the type is unspecified, it's fine for misuse to be non-portable."
45+
</p>
46+
<p>
47+
"Would like a diagnostic, don't care about SFINAE. Not clear to me that the current
48+
`setfill` wording disallows the mixed-character-type case at all ..."
49+
</p>
50+
<p>
51+
"NAD, not been a problem for a quarter of a century."
52+
</p>
3853
</discussion>
3954

4055
<resolution>

0 commit comments

Comments
 (0)