Skip to content

Set status for 4397 and 4404 #487

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jwakely merged 2 commits into from
Oct 20, 2025
Merged

Set status for 4397 and 4404 #487

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
51e4662
Set 4397 to P3, unclear if this should go to LEWG
tomaszkam Oct 20, 2025
bcf12ef
Set 4404 to Tentatively NAD
tomaszkam Oct 20, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 14 additions & 1 deletion xml/issue4397.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,14 +6,27 @@
<section><sref ref="[span.cons]"/></section>
<submitter>Hewill Kang</submitter>
<date>02 Oct 2025</date>
<priority>99</priority>
<priority>3</priority>

<discussion>
<p>
It is preferable to reject <code>span&lt;int, 42&gt;(views::empty&lt;int&gt;)</code>
at compile-time after <paper num="P2280R4"/>, since applying `ranges::size` on those
ranges is a constant expression now.
</p>

<note>2025-10-20; Reflector poll.</note>
<p>
Set priority to 3 after reflector poll.
</p>
<p>
The opinions on reflector discussion where split regarding,
if this should be considered LEWG matter.
</p>
<p>
Question was raised, if <tt>ranges::size(r) == N</tt> is required
to be usable at compile-time for integer-class types.
</p>
</discussion>

<resolution>
Expand Down
7 changes: 6 additions & 1 deletion xml/issue4404.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
<?xml version='1.0' encoding='utf-8' standalone='no'?>
<!DOCTYPE issue SYSTEM "lwg-issue.dtd">

<issue num="4404" status="New">
<issue num="4404" status="Tentatively NAD">
<title>Should <code>span(R&amp;&amp;)</code> CTAD apply P2280?</title>
<section>
<sref ref="[span.deduct]"/>
Expand Down Expand Up @@ -53,6 +53,11 @@ auto r = std::array&lt;int, N&gt;{} | std::views::as_const; // as_const_view&lt;
auto s2 = to_span(r);
static_assert(std::same_as&lt;decltype(s2), std::span&lt;const int, N&gt;&gt;); // <span style="color:red;font-weight:bolder">fire, ok after this PR</span>
</pre></blockquote>

<note>2025-10-20 Reflector poll. Status changed: NAD &rarr; Tentatively NAD.</note>
<p>
This is breaking change, and we need a paper with analysis.
</p>
</discussion>

<resolution>
Expand Down