Merge branch 'master' of github.com:cplusplus/LWG

Author: Dani-Hub

xml/issue3044.xml

@@ -169,9 +169,7 @@ an exception to be thrown. &mdash; <i>end note</i>]<br/>
 </blockquote>
 
 <note>2022-04-25; Daniel rebases wording on <paper num="N4910"/></note>
-</discussion>
-
-<resolution>
+<superseded>
 <p>
 This wording is relative to <paper num="N4910"/>.
 </p>
@@ -212,6 +210,54 @@ a<ins>3</ins>.max_size()
 </li>
 
 </ol>
+</superseded>
+
+<note>2025-10-10; Jonathan provides improved wording</note>
+
+</discussion>
+
+<resolution>
+<p>
+This wording is relative to <paper num="N5014"/>.
+</p>
+
+<ol>
+<li><p>Change <sref ref="[allocator.requirements.general]"/> as indicated:</p>
+
+
+<blockquote>
+<p>
+-2- In subclause <sref ref="[allocator.requirements]"/>,
+</p>
+<ol style="list-style-type:none">
+<li><p>(2.1) &mdash; [&hellip;]</p></li>
+<li><p>[&hellip;]</p></li>
+<li><p>(2.6) &mdash; <tt>a</tt>, <tt>a1</tt>, <tt>a2</tt> denote lvalues of type <tt>X</tt>,</p></li>
+<li><p><ins>(?.?) &mdash; <tt>a3</tt> denotes an lvalue of type (possibly const) <tt>X</tt>,</ins></p></li>
+<li><p>[&hellip;]</p></li>
+</ol>
+<p>[&hellip;]</p>
+<pre>
+a<ins>3</ins>.max_size()
+</pre>
+<blockquote>
+<p>
+-50- <i>Result:</i> <tt>X::size_type</tt>
+<p/>
+-51- <i>Returns:</i> The largest value that can meaningfully be passed to <tt>X::allocate()</tt>.
+<p/>
+<ins>[<i>Note:</i> Larger values can cause an exception to be thrown. &mdash; <i>end note</i>]</ins>
+<p/>
+<ins>-?- <i>Throws:</i> Nothing.</ins>
+<p/>
+-52- <i>Remarks:</i> Default: <tt>numeric_limits&lt;size_type&gt;::max() / sizeof(value_type)</tt>
+</p>
+</blockquote>
+</blockquote>
+</li>
+
+</ol>
+
 </resolution>
 
 </issue>

xml/issue4398.xml

@@ -24,11 +24,13 @@ template<> inline constexpr bool enable_nonlocking_formatter_optimization&
 </pre></blockquote>
 </blockquote>
 <p>
-However, formatting an adaptor requires formatting of the underlying range, and we disable 
-the nonlocking_optimizations for all ranges.
+However, formatting an adaptor requires formatting of the underlying range
+in terms of `ranges::ref_view`, and we disable the nonlocking_optimizations for all ranges, including `ranges::ref_view`.
 <p/>
-This problem does not occur for the `flat_set`, `flat_map` adaptors, which are also ranges, and 
-do not have a specialized formatter.
+This problem does not occur for the `flat_set`, `flat_map` adaptors, which are
+also ranges, but unlike `stack` etc. they do not have a specialized formatter.
+They use the `formatter` specialization for ranges and we already disable the
+optimization for that formatter.
 <p/>
 The proposed wording has recently been implemented in 
 <a href="https://gcc.gnu.org/pipermail/libstdc++/2025-October/063758.html">gcc's libstdc++</a>.