Set priorities from reflector polls

jwakely · jwakely · commit 8346498b1cfc · 2025-08-29T18:49:45.000+01:00
diff --git a/xml/issue4223.xml b/xml/issue4223.xml
@@ -8,7 +8,7 @@
 </section>
 <submitter>Tomasz Kaminski</submitter>
 <date>14 Mar 2025</date>
-<priority>99</priority>
+<priority>2</priority>
 
 <discussion>
 <p>
@@ -36,6 +36,12 @@ auto tv = fm | std::views::transform(std::identity{}); // iterator value value_t
 std::map m3(tv.begin(), tv.end()); // <span style="color:red;font-weight:bolder">Ill-formed, deduces std::map&lt;int const&amp;, float&amp;&gt;</span>
 </pre></blockquote>
 
+
+<note>2025-08-29; Reflector poll</note>
+<p>
+Set priority to 2 after reflector poll.
+</p>
+
 </discussion>
 
 <resolution>
diff --git a/xml/issue4252.xml b/xml/issue4252.xml
@@ -6,7 +6,7 @@
 <section><sref ref="[derivation]"/></section>
 <submitter>Jiang An</submitter>
 <date>28 Apr 2025</date>
-<priority>99</priority>
+<priority>3</priority>
 
 <discussion>
 <p>
@@ -18,6 +18,13 @@ However, libc++ marks `join_view`'s iterator `final` for some reasons
 (<a href="https://reviews.llvm.org/D142811#inline-1383022">https://reviews.llvm.org/D142811#inline-1383022</a>). 
 Perhaps we should clarify that the `final`-ity of exposition-only class is unspecified.
 </p>
+
+<note>2025-08-29; Reflector poll</note>
+<p>
+Set priority to 3 after reflector poll.
+Votes for P2 (due to implementation divergence), NAD, and LEWG.
+</p>
+
 </discussion>
 
 <resolution>
diff --git a/xml/issue4303.xml b/xml/issue4303.xml
@@ -6,7 +6,7 @@
 <section><sref ref="[range.iter.op.distance]"/></section>
 <submitter>Jiang An</submitter>
 <date>24 Jul 2025</date>
-<priority>99</priority>
+<priority>4</priority>
 
 <discussion>
 <p>
@@ -24,6 +24,12 @@ imposed by <tt>sized_sentinel_for&lt;S, decay_t&lt;I&gt;&gt;</tt> are still unde
 <p/>
 I think we should only decay arrays and keep `volatile` for non-array arguments.
 </p>
+
+<note>2025-08-29; Reflector poll</note>
+<p>
+Set priority to 4 after reflector poll.
+</p>
+
 </discussion>
 
 <resolution>
diff --git a/xml/issue4306.xml b/xml/issue4306.xml
@@ -6,7 +6,7 @@
 <section><sref ref="[member.functions]"/></section>
 <submitter>Jiang An</submitter>
 <date>24 Jul 2025</date>
-<priority>99</priority>
+<priority>3</priority>
 
 <discussion>
 <p>
@@ -45,6 +45,12 @@ As shown by the example, the allowance in <sref ref="[member.functions]"/>/2 can
 <p/>
 So perhaps some wording change is necessary to guarantee the <i>Constraints</i> of member functions to be meaningful.
 </p>
+
+<note>2025-08-29; Reflector poll</note>
+<p>
+Set priority to 3 after reflector poll.
+</p>
+
 </discussion>
 
 <resolution>
diff --git a/xml/issue4308.xml b/xml/issue4308.xml
@@ -8,7 +8,7 @@
 </section>
 <submitter>Jiang An</submitter>
 <date>05 Aug 2025</date>
-<priority>99</priority>
+<priority>1</priority>
 
 <discussion>
 <p>
@@ -22,6 +22,17 @@ random access iterator, and additional models `contiguous_iterator` when `T` is
 When `T` is a function type, the possibly intended iterator would be not even an actual iterator. 
 But it seems that range-for loop over such an <tt>std::optional&lt;T&amp;&gt;</tt> can work.
 </p>
+
+<note>2025-08-29; Reflector poll</note>
+<p>
+Set priority to 1 after reflector poll.
+</p>
+<p>
+"How can `end()` work for a pointer to incomplete type? `begin`/`end` should
+be constrained on object types, and Mandate complete object types.
+The aliases shouldn't be defined for non-object types, but probably harmless."
+</p>
+
 </discussion>
 
 <resolution>
