Skip to content

Set priorites for 4314 and 4021 #488

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 21, 2025
Merged

Set priorites for 4314 and 4021 #488

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
0ece2e9
Set priority of 4314 to P2
tomaszkam Oct 21, 2025
34bc5d1
Set priority of 4021 to P3
tomaszkam Oct 21, 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
20 changes: 19 additions & 1 deletion xml/issue4021.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@
<section><sref ref="[mdspan.mdspan.overview]"/></section>
<submitter>Stephan T. Lavavej</submitter>
<date>07 Dec 2023</date>
<priority>99</priority>
<priority>3</priority>

<discussion>
<p>
Expand Down Expand Up @@ -72,6 +72,24 @@ A type <tt>M</tt> meets the <i>layout mapping</i> requirements if
<p>
Constant expressions can surely be obtained without throwing exceptions.
</p>

<note>2025-10-21; Reflector poll.</note>
<p>
Set priority to 3 after reflector poll.
</p>
<p>
Use <tt>if consteval</tt> may lead to exception thrown from invocation
of <tt>is_always_<i>meow</i></tt>, when evaluated at runtime.
</p>
<p>
Design intent was for <tt>is_always_<i>meow</i></tt> functions to always
produce value at compile time. Layout requirements may need to be updated.
</p>
<p>
Separately, <sref ref="[structure.specifications]"/> says that
<i>Result:</i> is just the type and value category; not "constant expression"
- this matters because we need to require a prvalue constant expression here.
</p>
</discussion>

<resolution>
Expand Down
15 changes: 14 additions & 1 deletion xml/issue4314.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@
</section>
<submitter>Luc Grosheintz</submitter>
<date>13 Aug 2025</date>
<priority>99</priority>
<priority>2</priority>

<discussion>
<p>
Expand Down Expand Up @@ -71,6 +71,19 @@ This inconsistency was noticed while fixing
<a href="https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121061">PR121061</a>
and these changes have been applied to all layout mappings implemented in libstdc++.
</p>

<note>2025-10-21; Reflector poll.</note>
<p>
Set priority to 2 after reflector poll.
</p>
<p>
The resolution bypasses <tt>extents_type::<i>index-cast</i></tt> that would
validate if input value is representable.
</p>
<p>
We should require convertibility without regard to const and
value category.
</p>
</discussion>

<resolution>
Expand Down