Skip to content

Commit 0d06c0e

Browse files
committed
New issue from Jonathan: Even more feature-test macros for fully freestanding features are not marked freestanding
1 parent 75d894d commit 0d06c0e

File tree

1 file changed

+36
-0
lines changed

1 file changed

+36
-0
lines changed

xml/issue4411.xml

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
<?xml version='1.0' encoding='utf-8' standalone='no'?>
2+
<!DOCTYPE issue SYSTEM "lwg-issue.dtd">
3+
4+
<issue num="4411" status="New">
5+
<title>Even more feature-test macros for fully freestanding features are not marked freestanding</title>
6+
<section><sref ref="[version.syn]"/></section>
7+
<submitter>Jonathan Wakely</submitter>
8+
<date>14 Oct 2025</date>
9+
<priority>99</priority>
10+
11+
<discussion>
12+
<p>
13+
During the review of LWG <iref ref="4286"/> it was noticed that the
14+
proposed resolution did not include a change to `__cpp_lib_ranges_indices`,
15+
which was added in Sofia by <paper num="P3060R3"/>
16+
(which was after the issue was opened).
17+
18+
It also doesn't change `__cpp_lib_constexpr_utility, and probably should do.
19+
20+
It doesn't change `__cpp_lib_tuple_like`,
21+
but that's less clear whether it should do.
22+
The relevant changes in
23+
<code>&lt;tuple&gt;</code> and <code>&lt;pair&gt;</code>
24+
are obviously available in a freestanding implementation,
25+
but the changes in
26+
<code>&lt;map&gt;</code> and <code>&lt;unordered_map&gt;</code>
27+
are not.
28+
</p>
29+
</discussion>
30+
31+
<resolution>
32+
<p>
33+
</p>
34+
</resolution>
35+
36+
</issue>

0 commit comments

Comments
 (0)