diff --git a/xml/issue4166.xml b/xml/issue4166.xml index b796957b37..9d1ce7473c 100644 --- a/xml/issue4166.xml +++ b/xml/issue4166.xml @@ -1,7 +1,7 @@ - + `concat_view::end()` should be more constrained in order to support noncopyable iterators
Yaito Kakeyama & Nana Sakisaka @@ -96,6 +96,12 @@ if constexpr ((semiregular<iterator_t<maybe-const<is-con 2025-03-05; Hewill Kang provides improved wording + +2025-10-23; Reflector poll. +

+Set status to Tentatively Ready after seven votes in favour during reflector poll. +

+ diff --git a/xml/issue4171.xml b/xml/issue4171.xml index dde3f97063..344c098515 100644 --- a/xml/issue4171.xml +++ b/xml/issue4171.xml @@ -1,7 +1,7 @@ - + P2609R3 breaks code that uses `views::zip` and <tt>get<T></tt>
S. B. Tam @@ -39,6 +39,13 @@ an explicit return type to `fun`.

Did LWG foresee this impact of ? Could P2609R3 be reverted to unbreak this code pattern?

+ +2025-10-23; Reflector pool; Status changed: New → Tentatively NAD. +

+The range concepts are over-constrained by design, and `indirect_unary_invocable` +always required invocability with `iter_value_t`. The P2609 changes enforced this +requirement properly for iterators returning proxy references, including `zip_iterator`. +

diff --git a/xml/issue4220.xml b/xml/issue4220.xml index 5f46df0575..fe90ca1b76 100644 --- a/xml/issue4220.xml +++ b/xml/issue4220.xml @@ -8,7 +8,7 @@ Hewill Kang 06 Mar 2025 -99 +3

@@ -38,6 +38,15 @@ The proposed resolution preserves the inner range's original qualifiers, which i cache_latest_view stores the reference when it is a prvalue. The same goes for join_with_view.

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

+Set priority to 3 after reflector poll. +

+

+Lot of NAD votes. This type satisfies, but does not model +range. +

 diff --git a/xml/issue4271.xml b/xml/issue4271.xml index b966fddb79..f758701657 100644 --- a/xml/issue4271.xml +++ b/xml/issue4271.xml @@ -1,7 +1,7 @@ - + Caching range views claim amortized amortized 𝒪(1) runtime complexity for algorithms that are in fact 𝒪(n)
@@ -42,6 +42,17 @@ views (such as hypothetical non-caching variants of the affected views) that were previously considered invalid will become valid with these changes.

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

+Relaxing complexity of `ranges::begin`/`ranges::end` is design change, +and not direction we want to pursue. +

+

+The "amortized constant" are not quite right words to describe +intended requirements. A rework preserving the intent of current wording +would be welcomed. +

diff --git a/xml/issue4307.xml b/xml/issue4307.xml index aa01b4fb2e..1510498385 100644 --- a/xml/issue4307.xml +++ b/xml/issue4307.xml @@ -15,7 +15,7 @@ in <ranges>
Hewill Kang 28 Jul 2025 -99 +4

@@ -36,6 +36,15 @@ which would also allow newly introduced adapters or other library features to ta Note that since some of these simplifications change the order in which the concepts are spelled, they may not be purely editorial.

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

+Set priority to 4 after reflector poll. +

+

+Use of exposition-only concepts is not necessary improving readability +or produced error messages. +

 diff --git a/xml/issue4389.xml b/xml/issue4389.xml index 875b50d6f8..5272bdd0c5 100644 --- a/xml/issue4389.xml +++ b/xml/issue4389.xml @@ -1,12 +1,12 @@ - + `ranges::for_each` possibly behaves differently from range-based `for`
Jiang An 28 Sep 2025 -99 +2

@@ -29,6 +29,13 @@ implementation to tell whether a class has member `begin/end` but the correspond call is ill-formed with C++20 core language rules, and such determination is critical for eliminating the semantic differences between `ranges::for_each` and range-for.

+ +2025-10-23; Reflector poll; Status changed: New → SG9 and P2. +

+This is certainly evoluationary question and should go to LEWG/SG9. +It would disallow having unrelated begin/end members, where the range +interface is provided by hidden friends instead of those members. +

 diff --git a/xml/issue4401.xml b/xml/issue4401.xml index 4fb4ec53dd..59719896cd 100644 --- a/xml/issue4401.xml +++ b/xml/issue4401.xml @@ -1,7 +1,7 @@ - + `join_view` should be `sized_range` when applied to ranges of `simd::vec`
@@ -10,7 +10,7 @@
Hewill Kang 02 Oct 2025 -99 +3

@@ -33,6 +33,15 @@ In <ranges>, we use the tiny-range concep to consider types that can obtain static sizes specifically, and `simd::vec` seems to be a good fit.

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

+Introducting statically sized ranges and handling them in views, should be +handle as a paper. +

+

+The proposed change is also relevant to fixed-size span. +

 diff --git a/xml/issue4405.xml b/xml/issue4405.xml index 776c0884ac..af78af6457 100644 --- a/xml/issue4405.xml +++ b/xml/issue4405.xml @@ -8,7 +8,7 @@ Hewill Kang 05 Oct 2025 -99 +3

@@ -32,6 +32,16 @@ Given that we intend to reject object slicing for both `default_accessor` and `aligned_accessor`, there seems no reason not to reject this invalid pointer arithmetic for `mdspan`.

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

+Set priority to 3 after reflector poll. +

+

+Even if `data_handle_type` is a pointer to `value_type`, this does not mean +that it points to contiguous range of `value_type` objects. Accessor may +provide different access parttern. +