From c69cc95a71d90e3c403d1db77d02eef851b6b6e0 Mon Sep 17 00:00:00 2001 From: timsong-cpp Date: Wed, 5 Nov 2025 17:42:00 -1000 Subject: [PATCH] Update PR for 4260 --- xml/issue4260.xml | 38 +++++++++++++++++++++++++++++++++++--- 1 file changed, 35 insertions(+), 3 deletions(-) diff --git a/xml/issue4260.xml b/xml/issue4260.xml index befe333949..8fcf90e51f 100644 --- a/xml/issue4260.xml +++ b/xml/issue4260.xml @@ -30,9 +30,7 @@ If we want to mandate nothrow construction (a.k.a the implementation isn't out to get you), I'd rather we do it for all CPOs."

- - - +

This wording is relative to .

@@ -53,6 +51,40 @@ A query imposes syntactic and semantic requirements on its invocations. +
+ +2025-11-05; Tim provides improved wording +

+LWG decided to guarantee some additional properties for CPOs. +

+ + + +

+This wording is relative to . +

+
    + +
  1. Modify as indicated:

    + +
    +

    +-1- A customization point object is a function object () +with a literal class type that interacts with program-defined types +while enforcing semantic requirements on that interaction. +

    +

    +-2- The type of a customization point object, ignoring cv-qualifiers, +shall model `semiregular` () +and shall be a structural type () +and a trivially copyable type (). +Every constructor of this type +shall have a non-throwing exception specification (). +

    +
    +
  2. +
+