diff --git a/xml/issue4323.xml b/xml/issue4323.xml index ad3f9c7499..e76655f8ac 100644 --- a/xml/issue4323.xml +++ b/xml/issue4323.xml @@ -8,7 +8,7 @@ Matt Bentley 24 Aug 2025 -99 +3

@@ -39,6 +39,12 @@ This is a separate but related issue to LWG , but it would affect the outcome wording of that issue for `unique`.

+ +2025-10-22; Reflector poll. +

+Set priority to 3 after reflector poll. +

+ diff --git a/xml/issue4371.xml b/xml/issue4371.xml index 7c417b4d28..bf653da4ba 100644 --- a/xml/issue4371.xml +++ b/xml/issue4371.xml @@ -1,7 +1,7 @@ - + Container adaptor's `empty`/`size` should be `noexcept`
@@ -25,6 +25,13 @@ explicitly say those two members of the container must not throw, the fact that containers and common third-party containers mark them as unconditionally `noexcept` implies that it's perfectly reasonable to assume that they never will.

+ +2025-10-22 Reflector poll. Status changed: New → Tentatively NAD. +

+General disagrement with the proposed change. +Implicitly changing container requirements. +We should fix `flat_` adaptors instead. +

diff --git a/xml/issue4379.xml b/xml/issue4379.xml index eae5265a70..6e3577f865 100644 --- a/xml/issue4379.xml +++ b/xml/issue4379.xml @@ -8,7 +8,7 @@
Matt Bentley 17 Sep 2025 -99 +3

@@ -32,6 +32,15 @@ being > max_size. This is currently not stated in the Throws: element. I've implemented the requested additional throws and they are easily achievable.

+ +2025-10-22; Reflector poll. +

+Set priority to 3 after reflector poll. +

+

+There was discussion if `reserve()` is allowed to deallocate unused blocks, +that materialized into LWG . +

 diff --git a/xml/issue4380.xml b/xml/issue4380.xml index 7262952ad6..f546433f2f 100644 --- a/xml/issue4380.xml +++ b/xml/issue4380.xml @@ -9,7 +9,7 @@ Matt Bentley 23 Sep 2025 -99 +3

@@ -28,6 +28,15 @@ No-one has objected to this before, but if you want to, please speak up.

Anyway, the Complexity of `reserve()` does not presently reflect this ability.

+ +2025-10-22; Reflector poll. +

+Set priority to 3 after reflector poll. +

+

+An explicit objection was raised that the Effects: should state +whether `reserve()` is allowed, or even required, to deallocate blocks. +

 diff --git a/xml/issue4396.xml b/xml/issue4396.xml index 12a78abde8..e73eff11e5 100644 --- a/xml/issue4396.xml +++ b/xml/issue4396.xml @@ -1,12 +1,12 @@ - + Improve <code>inplace_vector(from_range_t, R&& rg)</code>
Hewill Kang 01 Oct 2025 -99 +3

@@ -24,6 +24,16 @@ capacity of `inplace_vector`. However, we should reject it at compile time since Given that we do a lot of compile-time size checking in <simd>, it's worth applying that here as well. Compile-time errors are better than runtime ones.

+ +2025-10-22; Reflector poll. Status changed: New → LEWG and P3. +

+General support for change, after LEWG approval. +

+

+Suggestion was made that this could be extended to all containers, +but is unlikely to be triggred in real word, as it requires ranges +with static size greater than `size_t(-1)`. +

 diff --git a/xml/issue4420.xml b/xml/issue4420.xml index 963f267d53..15076dd821 100644 --- a/xml/issue4420.xml +++ b/xml/issue4420.xml @@ -7,7 +7,7 @@ incorrectly constrained for <stdfloat> types
Matthias Kretz 15 Oct 2025 -99 +1

@@ -60,6 +60,21 @@ to `float` should do, so it needs to be added (again without breaking float equivalent constraints.

+2025-10-22; Reflector poll. +

+Set priority to 1 after reflector poll. +

+

+We also need to update Effects. There are more places in +where float to float16_t and similar conversion are not supported. +

+

+It was pointed out that similar issues happen for complex<float16_t>. +There seem to be mismatch between language initialization rules and the intended +usage based on library API. +

+ +

This wording is relative to .