Skip to content

Commit ef9fb00

Browse files
committed
Set 4387 to P3, unclear if this should go to LEWG
1 parent 47b1315 commit ef9fb00

File tree

1 file changed

+14
-1
lines changed

1 file changed

+14
-1
lines changed

xml/issue4397.xml

Lines changed: 14 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,14 +6,27 @@
66
<section><sref ref="[span.cons]"/></section>
77
<submitter>Hewill Kang</submitter>
88
<date>02 Oct 2025</date>
9-
<priority>99</priority>
9+
<priority>3</priority>
1010

1111
<discussion>
1212
<p>
1313
It is preferable to reject <code>span&lt;int, 42&gt;(views::empty&lt;int&gt;)</code>
1414
at compile-time after <paper num="P2280R4"/>, since applying `ranges::size` on those
1515
ranges is a constant expression now.
1616
</p>
17+
18+
<note>2025-10-20; Reflector poll.</note>
19+
<p>
20+
Set priority to 3 after reflector poll.
21+
</p>
22+
<p>
23+
The opinions on reflector discussion where split regarding,
24+
if this should be considered LEWG matter.
25+
</p>
26+
<p>
27+
Question was raised, if <tt>ranges::size(r) == N</tt> is required
28+
to be usable at compile-time for integer-class types.
29+
</p>
1730
</discussion>
1831

1932
<resolution>

0 commit comments

Comments
 (0)