[expr.compound] - C++23 → Trunk

Files changed (1) hide show

tmp/tmpx0v65ddf/{from.md → to.md} +797 -520

tmp/tmpx0v65ddf/{from.md → to.md} RENAMED Viewed

@@ -13,12 +13,14 @@ postfix-expression:
     postfix-expression '(' expression-listₒₚₜ ')'
     simple-type-specifier '(' expression-listₒₚₜ ')'
     typename-specifier '(' expression-listₒₚₜ ')'
     simple-type-specifier braced-init-list
     typename-specifier braced-init-list
-    postfix-expression '.' 'template'ₒₚₜ id-expression
-    postfix-expression '->' 'template'ₒₚₜ id-expression
     postfix-expression '++'
     postfix-expression '--'
     dynamic_cast '<' type-id '>' '(' expression ')'
     static_cast '<' type-id '>' '(' expression ')'
     reinterpret_cast '<' type-id '>' '(' expression ')'
@@ -41,23 +43,24 @@ replacing a `>>` token by two consecutive `>` tokens
 A *subscript expression* is a postfix expression followed by square
 brackets containing a possibly empty, comma-separated list of
 *initializer-clause*s that constitute the arguments to the subscript
 operator. The *postfix-expression* and the initialization of the object
-parameter of any applicable subscript operator function is sequenced
-before each expression in the *expression-list* and also before any
-default argument. The initialization of a non-object parameter of a
-subscript operator function `S` [[over.sub]], including every associated
-value computation and side effect, is indeterminately sequenced with
-respect to that of any other non-object parameter of `S`.
 With the built-in subscript operator, an *expression-list* shall be
 present, consisting of a single *assignment-expression*. One of the
 expressions shall be a glvalue of type “array of `T`” or a prvalue of
 type “pointer to `T`” and the other shall be a prvalue of unscoped
 enumeration or integral type. The result is of type “`T`”. The type
-“`T`” shall be a completely-defined object type.[^11]
 The expression `E1[E2]` is identical (by definition) to `*((E1)+(E2))`,
 except that in the case of an array operand, the result is an lvalue if
 that operand is an lvalue and an xvalue otherwise.
@@ -70,20 +73,20 @@ of array types. — *end note*]
 A function call is a postfix expression followed by parentheses
 containing a possibly empty, comma-separated list of
 *initializer-clause*s which constitute the arguments to the function.
-[*Note 1*: If the postfix expression is a function or member function
-name, the appropriate function and the validity of the call are
-determined according to the rules in  [[over.match]]. — *end note*]
 The postfix expression shall have function type or function pointer
 type. For a call to a non-member function or to a static member
-function, the postfix expression shall either be an lvalue that refers
 to a function (in which case the function-to-pointer standard conversion
-[[conv.func]] is suppressed on the postfix expression), or have function
-pointer type.
 If the selected function is non-virtual, or if the *id-expression* in
 the class member access expression is a *qualified-id*, that function is
 called. Otherwise, its final overrider [[class.virtual]] in the dynamic
 type of the object expression is called; such a call is referred to as a
@@ -92,14 +95,13 @@ type of the object expression is called; such a call is referred to as a
 [*Note 2*: The dynamic type is the type of the object referred to by
 the current value of the object expression. [[class.cdtor]] describes
 the behavior of virtual function calls when the object expression refers
 to an object under construction or destruction. — *end note*]
-[*Note 3*: If a function or member function name is used, and name
-lookup [[basic.lookup]] does not find a declaration of that name, the
-program is ill-formed. No function is implicitly declared by such a
-call. — *end note*]
 If the *postfix-expression* names a destructor or pseudo-destructor
 [[expr.prim.id.dtor]], the type of the function call expression is
 `void`; otherwise, the type of the function call expression is the
 return type of the statically chosen function (i.e., ignoring the
@@ -108,41 +110,44 @@ different. If the *postfix-expression* names a pseudo-destructor (in
 which case the *postfix-expression* is a possibly-parenthesized class
 member access), the function call destroys the object of scalar type
 denoted by the object expression of the class member access
 [[expr.ref]], [[basic.life]].
-Calling a function through an expression whose function type `E` is
-different from the function type `F` of the called function’s definition
-results in undefined behavior unless the type “pointer to `F`” can be
-converted to the type “pointer to `E`” via a function pointer conversion
-[[conv.fctptr]].
-[*Note 4*: The exception applies when the expression has the type of a
-potentially-throwing function, but the called function has a
 non-throwing exception specification, and the function types are
 otherwise the same. — *end note*]
 When a function is called, each parameter [[dcl.fct]] is initialized
-[[dcl.init]], [[class.copy.ctor]] with its corresponding argument. If
-the function is an explicit object member function and there is an
-implied object argument [[over.call.func]], the list of provided
-arguments is preceded by the implied object argument for the purposes of
-this correspondence. If there is no corresponding argument, the default
-argument for the parameter is used.
 [*Example 1*:
 ``` cpp
 template<typename ...T> int f(int n = 0, T ...t);
 int x = f<int>();               // error: no argument for second function parameter
 ```
 — *end example*]
-If the function is an implicit object member function, the `this`
-parameter of the function [[expr.prim.this]] is initialized with a
-pointer to the object of the call, converted as if by an explicit type
 conversion [[expr.cast]].
 [*Note 5*: There is no access or ambiguity checking on this conversion;
 the access checking and disambiguation are done as part of the (possibly
 implicit) class member access operator. See  [[class.member.lookup]],
@@ -153,28 +158,37 @@ class type that is either incomplete or abstract.
 [*Note 6*: This still allows a parameter to be a pointer or reference
 to such a type. However, it prevents a passed-by-value parameter to have
 an incomplete or abstract class type. — *end note*]
-It is *implementation-defined* whether the lifetime of a parameter ends
-when the function in which it is defined returns or at the end of the
-enclosing full-expression. The initialization and destruction of each
-parameter occurs within the context of the calling function.
-[*Example 2*: The access of the constructor, conversion functions or
-destructor is checked at the point of call in the calling function. If a
-constructor or destructor for a function parameter throws an exception,
-the search for a handler starts in the calling function; in particular,
-if the function called has a *function-try-block* [[except.pre]] with a
-handler that can handle the exception, this handler is not
 considered. — *end example*]
 The *postfix-expression* is sequenced before each *expression* in the
 *expression-list* and any default argument. The initialization of a
-parameter, including every associated value computation and side effect,
-is indeterminately sequenced with respect to that of any other
-parameter.
 [*Note 7*: All side effects of argument evaluations are sequenced
 before the function is entered (see
 [[intro.execution]]). — *end note*]
@@ -218,17 +232,26 @@ control out of the called function (if any), except in a virtual
 function call if the return type of the final overrider is different
 from the return type of the statically chosen function, the value
 returned from the final overrider is converted to the return type of the
 statically chosen function.
 [*Note 9*:  A function can change the values of its non-const
 parameters, but these changes cannot affect the values of the arguments
 except where a parameter is of a reference type [[dcl.ref]]; if the
-reference is to a const-qualified type, `const_cast` is required to be
-used to cast away the constness in order to modify the argument’s value.
-Where a parameter is of `const` reference type a temporary object is
-introduced if needed
 [[dcl.type]], [[lex.literal]], [[lex.string]], [[dcl.array]], [[class.temporary]].
 In addition, it is possible to modify the values of non-constant objects
 through pointer parameters. — *end note*]
 A function can be declared to accept fewer arguments (by declaring
@@ -254,15 +277,16 @@ The lvalue-to-rvalue [[conv.lval]], array-to-pointer [[conv.array]], and
 function-to-pointer [[conv.func]] standard conversions are performed on
 the argument expression. An argument that has type cv `std::nullptr_t`
 is converted to type `void*` [[conv.ptr]]. After these conversions, if
 the argument does not have arithmetic, enumeration, pointer,
 pointer-to-member, or class type, the program is ill-formed. Passing a
-potentially-evaluated argument of a scoped enumeration type or of a
-class type [[class]] having an eligible non-trivial copy constructor, an
-eligible non-trivial move constructor, or a non-trivial destructor
-[[special]], with no corresponding parameter, is conditionally-supported
-with *implementation-defined* semantics. If the argument has integral or
 enumeration type that is subject to the integral promotions
 [[conv.prom]], or a floating-point type that is subject to the
 floating-point promotion [[conv.fpprom]], the value of the argument is
 converted to the promoted type before the call. These promotions are
 referred to as the *default argument promotions*.
@@ -270,11 +294,13 @@ referred to as the *default argument promotions*.
 Recursive calls are permitted, except to the `main` function
 [[basic.start.main]].
 A function call is an lvalue if the result type is an lvalue reference
 type or an rvalue reference to function type, an xvalue if the result
-type is an rvalue reference to object type, and a prvalue otherwise.
 #### Explicit type conversion (functional notation) <a id="expr.type.conv">[[expr.type.conv]]</a>
 A *simple-type-specifier* [[dcl.type.simple]] or *typename-specifier*
 [[temp.res]] followed by a parenthesized optional *expression-list* or
@@ -283,11 +309,28 @@ specified type given the initializer. If the type is a placeholder for a
 deduced class type, it is replaced by the return type of the function
 selected by overload resolution for class template deduction
 [[over.match.class.deduct]] for the remainder of this subclause.
 Otherwise, if the type contains a placeholder type, it is replaced by
 the type determined by placeholder type deduction
-[[dcl.type.auto.deduct]].
 [*Example 1*:
 ``` cpp
 struct A {};
@@ -301,44 +344,41 @@ void h() {
 }
 ```
 — *end example*]
-If the initializer is a parenthesized single expression, the type
-conversion expression is equivalent to the corresponding cast expression
-[[expr.cast]]. Otherwise, if the type is cv `void` and the initializer
-is `()` or `{}` (after pack expansion, if any), the expression is a
-prvalue of type `void` that performs no initialization. Otherwise, the
-expression is a prvalue of the specified type whose result object is
-direct-initialized [[dcl.init]] with the initializer. If the initializer
-is a parenthesized optional *expression-list*, the specified type shall
-not be an array type.
 #### Class member access <a id="expr.ref">[[expr.ref]]</a>
 A postfix expression followed by a dot `.` or an arrow `->`, optionally
 followed by the keyword `template`, and then followed by an
-*id-expression*, is a postfix expression. The postfix expression before
-the dot or arrow is evaluated;[^12]
-the result of that evaluation, together with the *id-expression*,
-determines the result of the entire postfix expression.
-[*Note 1*: If the keyword `template` is used, the following unqualified
-name is considered to refer to a template [[temp.names]]. If a
-*simple-template-id* results and is followed by a `::`, the
-*id-expression* is a *qualified-id*. — *end note*]
-For the first option (dot) the first expression shall be a glvalue. For
-the second option (arrow) the first expression shall be a prvalue having
-pointer type. The expression `E1->E2` is converted to the equivalent
-form `(*(E1)).E2`; the remainder of [[expr.ref]] will address only the
-first option (dot).[^13]
-Abbreviating *postfix-expression*`.`*id-expression* as `E1.E2`, `E1` is
-called the *object expression*. If the object expression is of scalar
-type, `E2` shall name the pseudo-destructor of that same type (ignoring
 cv-qualifications) and `E1.E2` is a prvalue of type “function of ()
 returning `void`”.
 [*Note 2*: This value can only be used for a notional function call
 [[expr.prim.id.dtor]]. — *end note*]
@@ -351,68 +391,105 @@ definition of that class.
 when the class is complete [[class.member.lookup]]. — *end note*]
 [*Note 4*:  [[basic.lookup.qual]] describes how names are looked up
 after the `.` and `->` operators. — *end note*]
-If `E2` is a bit-field, `E1.E2` is a bit-field. The type and value
-category of `E1.E2` are determined as follows. In the remainder of
-[[expr.ref]], *cq* represents either `const` or the absence of `const`
-and *vq* represents either `volatile` or the absence of `volatile`. *cv*
-represents an arbitrary set of cv-qualifiers, as defined in
-[[basic.type.qualifier]].
-If `E2` is declared to have type “reference to `T`”, then `E1.E2` is an
-lvalue of type `T`. If `E2` is a static data member, `E1.E2` designates
-the object or function to which the reference is bound, otherwise
-`E1.E2` designates the object or function to which the corresponding
-reference member of `E1` is bound. Otherwise, one of the following rules
-applies.
-- If `E2` is a static data member and the type of `E2` is `T`, then
- `E1.E2` is an lvalue; the expression designates the named member of
-  the class. The type of `E1.E2` is `T`.
-- If `E2` is a non-static data member and the type of `E1` is “*cq1 vq1*
-  `X`”, and the type of `E2` is “*cq2 vq2* `T`”, the expression
-  designates the corresponding member subobject of the object designated
-  by the first expression. If `E1` is an lvalue, then `E1.E2` is an
-  lvalue; otherwise `E1.E2` is an xvalue. Let the notation *vq12* stand
- for the “union” of *vq1* and *vq2*; that is, if *vq1* or *vq2* is
- `volatile`, then *vq12* is `volatile`. Similarly, let the notation
-  *cq12* stand for the “union” of *cq1* and *cq2*; that is, if *cq1* or
- *cq2* is `const`, then *cq12* is `const`. If `E2` is declared to be a
- `mutable` member, then the type of `E1.E2` is “*vq12* `T`”. If `E2` is
- not declared to be a `mutable` member, then the type of `E1.E2` is
- “*cq12* *vq12* `T`”.
-- If `E2` is an overload set, function overload resolution
- [[over.match]] is used to select the function to which `E2` refers.
- The type of `E1.E2` is the type of `E2` and `E1.E2` refers to the
- function referred to by `E2`.
   - If `E2` refers to a static member function, `E1.E2` is an lvalue.
   - Otherwise (when `E2` refers to a non-static member function),
-    `E1.E2` is a prvalue. The expression can be used only as the
- left-hand operand of a member function call [[class.mfct]].
- \[*Note 5*: Any redundant set of parentheses surrounding the
-    expression is ignored [[expr.prim.paren]]. — *end note*]
-- If `E2` is a nested type, the expression `E1.E2` is ill-formed.
-- If `E2` is a member enumerator and the type of `E2` is `T`, the
-  expression `E1.E2` is a prvalue of type `T` whose value is the value
-  of the enumerator.
-If `E2` is a non-static member, the program is ill-formed if the class
-of which `E2` is directly a member is an ambiguous base
-[[class.member.lookup]] of the naming class [[class.access.base]] of
-`E2`.
-[*Note 6*: The program is also ill-formed if the naming class is an
 ambiguous base of the class type of the object expression; see
 [[class.access.base]]. — *end note*]
-If `E2` is a non-static member and the result of `E1` is an object whose
-type is not similar [[conv.qual]] to the type of `E1`, the behavior is
-undefined.
-[*Example 1*:
 ``` cpp
 struct A { int i; };
 struct B { int j; };
 struct D : A, B {};
@@ -425,33 +502,32 @@ void f() {
 — *end example*]
 #### Increment and decrement <a id="expr.post.incr">[[expr.post.incr]]</a>
-The value of a postfix `++` expression is the value of its operand.
 [*Note 1*: The value obtained is a copy of the original
 value. — *end note*]
 The operand shall be a modifiable lvalue. The type of the operand shall
 be an arithmetic type other than cv `bool`, or a pointer to a complete
 object type. An operand with volatile-qualified type is deprecated; see
 [[depr.volatile.type]]. The value of the operand object is modified
-[[defns.access]] by adding `1` to it. The value computation of the `++`
-expression is sequenced before the modification of the operand object.
-With respect to an indeterminately-sequenced function call, the
-operation of postfix `++` is a single evaluation.
 [*Note 2*: Therefore, a function call cannot intervene between the
 lvalue-to-rvalue conversion and the side effect associated with any
 single postfix `++` operator. — *end note*]
 The result is a prvalue. The type of the result is the cv-unqualified
-version of the type of the operand. If the operand is a bit-field that
-cannot represent the incremented value, the resulting value of the
-bit-field is *implementation-defined*. See also  [[expr.add]] and
-[[expr.ass]].
 The operand of postfix `--` is decremented analogously to the postfix
 `++` operator.
 [*Note 3*: For prefix increment and decrement, see
@@ -479,11 +555,11 @@ If `T` is “pointer to *cv1* `B`” and `v` has type “pointer to *cv2* `D`”
 such that `B` is a base class of `D`, the result is a pointer to the
 unique `B` subobject of the `D` object pointed to by `v`, or a null
 pointer value if `v` is a null pointer value. Similarly, if `T` is
 “reference to *cv1* `B`” and `v` has type *cv2* `D` such that `B` is a
 base class of `D`, the result is the unique `B` subobject of the `D`
-object referred to by `v`.[^14]
 In both the pointer and reference cases, the program is ill-formed if
 `B` is an inaccessible or ambiguous base class of `D`.
 [*Example 1*:
@@ -501,10 +577,18 @@ void foo(D* dp) {
 Otherwise, `v` shall be a pointer to or a glvalue of a polymorphic type
 [[class.virtual]].
 If `v` is a null pointer value, the result is a null pointer value.
 If `T` is “pointer to cv `void`”, then the result is a pointer to the
 most derived object pointed to by `v`. Otherwise, a runtime check is
 applied to see if the object pointed or referred to by `v` can be
 converted to the type pointed or referred to by `T`.
@@ -512,11 +596,11 @@ Let `C` be the class type to which `T` points or refers. The runtime
 check logically executes as follows:
 - If, in the most derived object pointed (referred) to by `v`, `v`
   points (refers) to a public base class subobject of a `C` object, and
   if only one object of type `C` is derived from the subobject pointed
-  (referred) to by `v` the result points (refers) to that `C` object.
 - Otherwise, if `v` points (refers) to a public base class subobject of
   the most derived object, and the type of the most derived object has a
   base class, of type `C`, that is unambiguous and public, the result
   points (refers) to the `C` subobject of the most derived object.
 - Otherwise, the runtime check *fails*.
@@ -562,31 +646,35 @@ destruction. — *end note*]
 #### Type identification <a id="expr.typeid">[[expr.typeid]]</a>
 The result of a `typeid` expression is an lvalue of static type `const`
 `std::type_info` [[type.info]] and dynamic type `const` `std::type_info`
-or `const` *name* where *name* is an *implementation-defined* class
 publicly derived from `std::type_info` which preserves the behavior
-described in  [[type.info]].[^15]
 The lifetime of the object referred to by the lvalue extends to the end
 of the program. Whether or not the destructor is called for the
 `std::type_info` object at the end of the program is unspecified.
 If the type of the *expression* or *type-id* operand is a (possibly
 cv-qualified) class type or a reference to (possibly cv-qualified) class
 type, that class shall be completely defined.
 When `typeid` is applied to a glvalue whose type is a polymorphic class
 type [[class.virtual]], the result refers to a `std::type_info` object
 representing the type of the most derived object [[intro.object]] (that
-is, the dynamic type) to which the glvalue refers. If the glvalue is
-obtained by applying the unary `*` operator to a pointer[^16]
-and the pointer is a null pointer value [[basic.compound]], the `typeid`
-expression throws an exception [[except.throw]] of a type that would
-match a handler of type `std::bad_typeid` exception [[bad.typeid]].
 When `typeid` is applied to an expression other than a glvalue of a
 polymorphic class type, the result refers to a `std::type_info` object
 representing the static type of the expression. Lvalue-to-rvalue
 [[conv.lval]], array-to-pointer [[conv.array]], and function-to-pointer
@@ -599,11 +687,11 @@ When `typeid` is applied to a *type-id*, the result refers to a
 `std::type_info` object representing the type of the *type-id*. If the
 type of the *type-id* is a reference to a possibly cv-qualified type,
 the result of the `typeid` expression refers to a `std::type_info`
 object representing the cv-unqualified referenced type.
-[*Note 1*: The *type-id* cannot denote a function type with a
 *cv-qualifier-seq* or a *ref-qualifier* [[dcl.fct]]. — *end note*]
 If the type of the expression or *type-id* is a cv-qualified type, the
 result of the `typeid` expression refers to a `std::type_info` object
 representing the cv-unqualified type.
@@ -626,24 +714,23 @@ typeid(D)  == typeid(const D&); // yields true
 The type `std::type_info` [[type.info]] is not predefined; if a standard
 library declaration [[typeinfo.syn]], [[std.modules]] of
 `std::type_info` does not precede [[basic.lookup.general]] a `typeid`
 expression, the program is ill-formed.
-[*Note 2*: Subclause [[class.cdtor]] describes the behavior of `typeid`
 applied to an object under construction or destruction. — *end note*]
 #### Static cast <a id="expr.static.cast">[[expr.static.cast]]</a>
 The result of the expression `static_cast<T>(v)` is the result of
 converting the expression `v` to type `T`. If `T` is an lvalue reference
 type or an rvalue reference to function type, the result is an lvalue;
 if `T` is an rvalue reference to object type, the result is an xvalue;
-otherwise, the result is a prvalue. The `static_cast` operator shall not
-cast away constness [[expr.const.cast]].
 An lvalue of type “*cv1* `B`”, where `B` is a class type, can be cast to
-type “reference to *cv2* `D`”, where `D` is a class derived
 [[class.derived]] from `B`, if *cv2* is the same cv-qualification as, or
 greater cv-qualification than, *cv1*. If `B` is a virtual base class of
 `D` or a base class of a virtual base class of `D`, or if no valid
 standard conversion from “pointer to `D`” to “pointer to `B`” exists
 [[conv.ptr]], the program is ill-formed. An xvalue of type “*cv1* `B`”
@@ -674,14 +761,25 @@ class subobject thereof; otherwise, the lvalue-to-rvalue conversion
 used as the operand of the `static_cast` for the remainder of this
 subclause. If `T2` is an inaccessible [[class.access]] or ambiguous
 [[class.member.lookup]] base class of `T1`, a program that necessitates
 such a cast is ill-formed.
-An expression E can be explicitly converted to a type `T` if there is an
-implicit conversion sequence [[over.best.ics]] from E to `T`, if
-overload resolution for a direct-initialization [[dcl.init]] of an
-object or reference of type `T` from E would find at least one viable
 function [[over.match.viable]], or if `T` is an aggregate type
 [[dcl.init.aggr]] having a first element `x` and there is an implicit
 conversion sequence from E to the type of `x`. If `T` is a reference
 type, the effect is the same as performing the declaration and
 initialization
@@ -692,59 +790,23 @@ T t(E);
 for some invented temporary variable `t` [[dcl.init]] and then using the
 temporary variable as the result of the conversion. Otherwise, the
 result object is direct-initialized from E.
-[*Note 1*: The conversion is ill-formed when attempting to convert an
 expression of class type to an inaccessible or ambiguous base
 class. — *end note*]
-[*Note 2*: If `T` is “array of unknown bound of `U`”, this
 direct-initialization defines the type of the expression as
 `U[1]`. — *end note*]
-Otherwise, the `static_cast` shall perform one of the conversions listed
-below. No other conversion shall be performed explicitly using a
-`static_cast`.
-Any expression can be explicitly converted to type cv `void`, in which
-case the operand is a discarded-value expression [[expr.prop]].
-[*Note 3*: Such a `static_cast` has no result as it is a prvalue of
-type `void`; see  [[basic.lval]]. — *end note*]
-[*Note 4*: However, if the value is in a temporary object
-[[class.temporary]], the destructor for that object is not executed
-until the usual time, and the value of the object is preserved for the
-purpose of executing the destructor. — *end note*]
-The inverse of any standard conversion sequence [[conv]] not containing
-an lvalue-to-rvalue [[conv.lval]], array-to-pointer [[conv.array]],
-function-to-pointer [[conv.func]], null pointer [[conv.ptr]], null
-member pointer [[conv.mem]], boolean [[conv.bool]], or function pointer
-[[conv.fctptr]] conversion, can be performed explicitly using
-`static_cast`. A program is ill-formed if it uses `static_cast` to
-perform the inverse of an ill-formed standard conversion sequence.
-[*Example 2*:
-``` cpp
-struct B { };
-struct D : private B { };
-void f() {
-  static_cast<D*>((B*)0);               // error: B is a private base of D
-  static_cast<int B::*>((int D::*)0);   // error: B is a private base of D
-}
-```
-— *end example*]
-The lvalue-to-rvalue [[conv.lval]], array-to-pointer [[conv.array]], and
-function-to-pointer [[conv.func]] conversions are applied to the
-operand. Such a `static_cast` is subject to the restriction that the
-explicit conversion does not cast away constness [[expr.const.cast]],
-and the following additional rules for specific cases:
 A value of a scoped enumeration type [[dcl.enum]] can be explicitly
 converted to an integral type; the result is the same as that of
 converting to the enumeration’s underlying type and then to the
 destination type. A value of a scoped enumeration type can also be
@@ -797,14 +859,13 @@ pointer-to-member-function types) are never cv-qualified
 If no valid standard conversion from “pointer to member of `B` of type
 `T`” to “pointer to member of `D` of type `T`” exists [[conv.mem]], the
 program is ill-formed. The null member pointer value [[conv.mem]] is
 converted to the null member pointer value of the destination type. If
-class `B` contains the original member, or is a base or derived class of
-the class containing the original member, the resulting pointer to
-member points to the original member. Otherwise, the behavior is
-undefined.
 [*Note 6*: Although class `B` need not contain the original member, the
 dynamic type of the object with which indirection through the pointer to
 member is performed must contain the original member; see
 [[expr.mptr.oper]]. — *end note*]
@@ -812,17 +873,18 @@ member is performed must contain the original member; see
 A prvalue of type “pointer to *cv1* `void`” can be converted to a
 prvalue of type “pointer to *cv2* `T`”, where `T` is an object type and
 *cv2* is the same cv-qualification as, or greater cv-qualification than,
 *cv1*. If the original pointer value represents the address `A` of a
 byte in memory and `A` does not satisfy the alignment requirement of
-`T`, then the resulting pointer value is unspecified. Otherwise, if the
-original pointer value points to an object *a*, and there is an object
-*b* of type similar to `T` that is pointer-interconvertible
-[[basic.compound]] with *a*, the result is a pointer to *b*. Otherwise,
-the pointer value is unchanged by the conversion.
-[*Example 3*:
 ``` cpp
 T* p1 = new T;
 const T* p2 = static_cast<const T*>(static_cast<void*>(p1));
 bool b = p1 == p2;  // b will have the value true.
@@ -867,12 +929,12 @@ the conversion has the same meaning and validity as a conversion of
 any type to the type `std::nullptr_t`. — *end note*]
 A value of integral type or enumeration type can be explicitly converted
 to a pointer. A pointer converted to an integer of sufficient size (if
 any such exists on the implementation) and back to the same pointer type
-will have its original value; mappings between pointers and integers are
-otherwise *implementation-defined*.
 A function pointer can be explicitly converted to a function pointer of
 a different type.
 [*Note 4*: The effect of calling a function through a pointer to a
@@ -882,21 +944,18 @@ definition of the function is undefined [[expr.call]]. — *end note*]
 Except that converting a prvalue of type “pointer to `T1`” to the type
 “pointer to `T2`” (where `T1` and `T2` are function types) and back to
 its original type yields the original pointer value, the result of such
 a pointer conversion is unspecified.
-[*Note 5*: See also  [[conv.ptr]] for more details of pointer
-conversions. — *end note*]
 An object pointer can be explicitly converted to an object pointer of a
-different type.[^17]
 When a prvalue `v` of object pointer type is converted to the object
 pointer type “pointer to cv `T`”, the result is
 `static_cast<cv T*>(static_cast<cv~void*>(v))`.
-[*Note 6*: Converting a pointer of type “pointer to `T1`” that points
 to an object of type `T1` to the type “pointer to `T2`” (where `T2` is
 an object type and the alignment requirements of `T2` are no stricter
 than those of `T1`) and back to its original type yields the original
 pointer value. — *end note*]
@@ -908,19 +967,19 @@ other type and back, possibly with different cv-qualification, shall
 yield the original pointer value.
 The null pointer value [[basic.compound]] is converted to the null
 pointer value of the destination type.
-[*Note 7*: A null pointer constant of type `std::nullptr_t` cannot be
 converted to a pointer type, and a null pointer constant of integral
 type is not necessarily converted to a null pointer
 value. — *end note*]
 A prvalue of type “pointer to member of `X` of type `T1`” can be
 explicitly converted to a prvalue of a different type “pointer to member
 of `Y` of type `T2`” if `T1` and `T2` are both function types or both
-object types.[^18]
 The null member pointer value [[conv.mem]] is converted to the null
 member pointer value of the destination type. The result of this
 conversion is unspecified, except in the following cases:
@@ -931,79 +990,83 @@ conversion is unspecified, except in the following cases:
   `T1`” to the type “pointer to data member of `Y` of type `T2`” (where
   the alignment requirements of `T2` are no stricter than those of `T1`)
   and back to its original type yields the original pointer-to-member
   value.
-A glvalue of type `T1`, designating an object *x*, can be cast to the
-type “reference to `T2`” if an expression of type “pointer to `T1`” can
-be explicitly converted to the type “pointer to `T2`” using a
-`reinterpret_cast`. The result is that of `*reinterpret_cast<T2 *>(p)`
-where `p` is a pointer to *x* of type “pointer to `T1`”. No temporary is
-created, no copy is made, and no constructors [[class.ctor]] or
-conversion functions [[class.conv]] are called.[^19]
 #### Const cast <a id="expr.const.cast">[[expr.const.cast]]</a>
 The result of the expression `const_cast<T>(v)` is of type `T`. If `T`
 is an lvalue reference to object type, the result is an lvalue; if `T`
 is an rvalue reference to object type, the result is an xvalue;
 otherwise, the result is a prvalue and the lvalue-to-rvalue
 [[conv.lval]], array-to-pointer [[conv.array]], and function-to-pointer
 [[conv.func]] standard conversions are performed on the expression `v`.
-Conversions that can be performed explicitly using `const_cast` are
-listed below. No other conversion shall be performed explicitly using
-`const_cast`.
 [*Note 1*: Subject to the restrictions in this subclause, an expression
 can be cast to its own type using a `const_cast`
 operator. — *end note*]
-For two similar types `T1` and `T2` [[conv.qual]], a prvalue of type
-`T1` may be explicitly converted to the type `T2` using a `const_cast`
-if, considering the qualification-decompositions of both types, each P¹ᵢ
-is the same as P²ᵢ for all i. The result of a `const_cast` refers to the
-original entity.
-[*Example 1*:
-``` cpp
-typedef int *A[3];                  // array of 3 pointer to int
-typedef const int *const CA[3];     // array of 3 const pointer to const int
-CA &&r = A{};                       // OK, reference binds to temporary array object
-                                    // after qualification conversion to type CA
-A &&r1 = const_cast<A>(CA{});       // error: temporary array decayed to pointer
-A &&r2 = const_cast<A&&>(CA{});     // OK
-```
-— *end example*]
 For two object types `T1` and `T2`, if a pointer to `T1` can be
 explicitly converted to the type “pointer to `T2`” using a `const_cast`,
 then the following conversions can also be made:
 - an lvalue of type `T1` can be explicitly converted to an lvalue of
   type `T2` using the cast `const_cast<T2&>`;
 - a glvalue of type `T1` can be explicitly converted to an xvalue of
   type `T2` using the cast `const_cast<T2&&>`; and
-- if `T1` is a class type, a prvalue of type `T1` can be explicitly
-  converted to an xvalue of type `T2` using the cast `const_cast<T2&&>`.
-The result of a reference `const_cast` refers to the original object if
-the operand is a glvalue and to the result of applying the temporary
-materialization conversion [[conv.rval]] otherwise.
-A null pointer value [[basic.compound]] is converted to the null pointer
-value of the destination type. The null member pointer value
-[[conv.mem]] is converted to the null member pointer value of the
-destination type.
 [*Note 2*:
 Depending on the type of the object, a write operation through the
 pointer, lvalue or pointer to data member resulting from a `const_cast`
-that casts away a const-qualifier[^20]
 can produce undefined behavior [[dcl.type.cv]].
 — *end note*]
@@ -1049,10 +1112,11 @@ unary-expression:
     sizeof '...' '(' identifier ')'
     alignof '(' type-id ')'
     noexcept-expression
     new-expression
     delete-expression
 ```
 ``` bnf
 %% Ed. note: character protrusion would misalign operators.
@@ -1062,33 +1126,42 @@ unary-operator: one of
 #### Unary operators <a id="expr.unary.op">[[expr.unary.op]]</a>
 The unary `*` operator performs *indirection*. Its operand shall be a
 prvalue of type “pointer to `T`”, where `T` is an object or function
-type. The operator yields an lvalue of type `T` denoting the object or
-function to which the operand points.
-[*Note 1*: Indirection through a pointer to an incomplete type (other
 than cv `void`) is valid. The lvalue thus obtained can be used in
 limited ways (to initialize a reference, for example); this lvalue must
 not be converted to a prvalue, see  [[conv.lval]]. — *end note*]
 Each of the following unary operators yields a prvalue.
 The operand of the unary `&` operator shall be an lvalue of some type
-`T`. The result is a prvalue.
-- If the operand is a *qualified-id* naming a non-static or variant
-  member `m` of some class `C`, other than an explicit object member
-  function, the result has type “pointer to member of class `C` of type
- `T`” and designates `C::m`.
 - Otherwise, the result has type “pointer to `T`” and points to the
   designated object [[intro.memory]] or function [[basic.compound]]. If
-  the operand names an explicit object member function [[dcl.fct]], the
-  operand shall be a *qualified-id*. \[*Note 2*: In particular, taking
- the address of a variable of type “cv `T`” yields a pointer of type
-  “pointer to cv `T`”. — *end note*]
 [*Example 1*:
 ``` cpp
 struct A { int i; };
@@ -1100,18 +1173,19 @@ int* p2 = p1 + 1;   // defined behavior
 bool b = p2 > p1;   // defined behavior, with value true
 ```
 — *end example*]
-[*Note 3*: A pointer to member formed from a `mutable` non-static data
 member [[dcl.stc]] does not reflect the `mutable` specifier associated
 with the non-static data member. — *end note*]
 A pointer to member is only formed when an explicit `&` is used and its
-operand is a *qualified-id* not enclosed in parentheses.
-[*Note 4*: That is, the expression `&(qualified-id)`, where the
 *qualified-id* is enclosed in parentheses, does not form an expression
 of type “pointer to member”. Neither does `qualified-id`, because there
 is no implicit conversion from a *qualified-id* for a non-static member
 function to the type “pointer to member function” as there is from an
 lvalue of function type to the type “pointer to function” [[conv.func]].
@@ -1121,99 +1195,96 @@ the *unqualified-id*’s class. — *end note*]
 If `&` is applied to an lvalue of incomplete class type and the complete
 type declares `operator&()`, it is unspecified whether the operator has
 the built-in meaning or the operator function is called. The operand of
 `&` shall not be a bit-field.
-[*Note 5*: The address of an overload set [[over]] can be taken only in
 a context that uniquely determines which function is referred to (see
 [[over.over]]). Since the context can affect whether the operand is a
 static or non-static member function, the context can also affect
 whether the expression has type “pointer to function” or “pointer to
 member function”. — *end note*]
-The operand of the unary `+` operator shall have arithmetic, unscoped
-enumeration, or pointer type and the result is the value of the
 argument. Integral promotion is performed on integral or enumeration
 operands. The type of the result is the type of the promoted operand.
-The operand of the unary `-` operator shall have arithmetic or unscoped
-enumeration type and the result is the negative of its operand. Integral
-promotion is performed on integral or enumeration operands. The negative
-of an unsigned quantity is computed by subtracting its value from 2ⁿ,
-where n is the number of bits in the promoted operand. The type of the
-result is the type of the promoted operand.
-[*Note 6*: The result is the two’s complement of the operand (where
 operand and result are considered as unsigned). — *end note*]
 The operand of the logical negation operator `!` is contextually
 converted to `bool` [[conv]]; its value is `true` if the converted
 operand is `false` and `false` otherwise. The type of the result is
 `bool`.
-The operand of the `~` operator shall have integral or unscoped
-enumeration type. Integral promotions are performed. The type of the
-result is the type of the promoted operand. Given the coefficients `xᵢ`
-of the base-2 representation [[basic.fundamental]] of the promoted
-operand `x`, the coefficient `rᵢ` of the base-2 representation of the
-result `r` is 1 if `xᵢ` is 0, and 0 otherwise.
-[*Note 7*: The result is the ones’ complement of the operand (where
 operand and result are considered as unsigned). — *end note*]
 There is an ambiguity in the grammar when `~` is followed by a
-*type-name* or *decltype-specifier*. The ambiguity is resolved by
 treating `~` as the operator rather than as the start of an
 *unqualified-id* naming a destructor.
-[*Note 8*: Because the grammar does not permit an operator to follow
 the `.`, `->`, or `::` tokens, a `~` followed by a *type-name* or
-*decltype-specifier* in a member access expression or *qualified-id* is
-unambiguously parsed as a destructor name. — *end note*]
 #### Increment and decrement <a id="expr.pre.incr">[[expr.pre.incr]]</a>
-The operand of prefix `++` is modified [[defns.access]] by adding `1`.
-The operand shall be a modifiable lvalue. The type of the operand shall
-be an arithmetic type other than cv `bool`, or a pointer to a
-completely-defined object type. An operand with volatile-qualified type
-is deprecated; see  [[depr.volatile.type]]. The result is the updated
-operand; it is an lvalue, and it is a bit-field if the operand is a
-bit-field. The expression `++x` is equivalent to `x+=1`.
-[*Note 1*: See the discussions of addition [[expr.add]] and assignment
-operators [[expr.ass]] for information on conversions. — *end note*]
-The operand of prefix `--` is modified [[defns.access]] by subtracting
-`1`. The requirements on the operand of prefix `--` and the properties
-of its result are otherwise the same as those of prefix `++`.
-[*Note 2*: For postfix increment and decrement, see
 [[expr.post.incr]]. — *end note*]
 #### Await <a id="expr.await">[[expr.await]]</a>
 The `co_await` expression is used to suspend evaluation of a coroutine
 [[dcl.fct.def.coroutine]] while awaiting completion of the computation
-represented by the operand expression.
 ``` bnf
 await-expression:
- 'co_await' cast-expression
 ```
-An *await-expression* shall appear only in a potentially-evaluated
-expression within the *compound-statement* of a *function-body* outside
-of a *handler* [[except.pre]]. In a *declaration-statement* or in the
 *simple-declaration* (if any) of an *init-statement*, an
 *await-expression* shall appear only in an *initializer* of that
 *declaration-statement* or *simple-declaration*. An *await-expression*
 shall not appear in a default argument [[dcl.fct.default]]. An
 *await-expression* shall not appear in the initializer of a block
-variable with static or thread storage duration. A context within a
-function where an *await-expression* can appear is called a *suspension
-context* of the function.
 Evaluation of an *await-expression* involves the following auxiliary
 types, expressions, and objects:
 - *p* is an lvalue naming the promise object [[dcl.fct.def.coroutine]]
@@ -1333,11 +1404,11 @@ to any other fundamental type [[basic.fundamental]] is
 [*Note 1*:
 In particular, the values of `sizeof(bool)`, `sizeof(char16_t)`,
 `sizeof(char32_t)`, and `sizeof(wchar_t)` are
-implementation-defined.[^21]
 — *end note*]
 [*Note 2*: See  [[intro.memory]] for the definition of byte and
 [[term.object.representation]] for the definition of object
@@ -1346,83 +1417,84 @@ representation. — *end note*]
 When applied to a reference type, the result is the size of the
 referenced type. When applied to a class, the result is the number of
 bytes in an object of that class including any padding required for
 placing objects of that type in an array. The result of applying
 `sizeof` to a potentially-overlapping subobject is the size of the type,
-not the size of the subobject.[^22]
 When applied to an array, the result is the total number of bytes in the
 array. This implies that the size of an array of n elements is n times
 the size of an element.
 The lvalue-to-rvalue [[conv.lval]], array-to-pointer [[conv.array]], and
 function-to-pointer [[conv.func]] standard conversions are not applied
 to the operand of `sizeof`. If the operand is a prvalue, the temporary
 materialization conversion [[conv.rval]] is applied.
-The identifier in a `sizeof...` expression shall name a pack. The
 `sizeof...` operator yields the number of elements in the pack
 [[temp.variadic]]. A `sizeof...` expression is a pack expansion
 [[temp.variadic]].
 [*Example 1*:
 ``` cpp
 template<class... Types>
 struct count {
-  static const std::size_t value = sizeof...(Types);
 };
 ```
 — *end example*]
 The result of `sizeof` and `sizeof...` is a prvalue of type
 `std::size_t`.
 [*Note 3*: A `sizeof` expression is an integral constant expression
-[[expr.const]]. The type `std::size_t` is defined in the standard header
-`<cstddef>` [[cstddef.syn]], [[support.types.layout]]. — *end note*]
 #### Alignof <a id="expr.alignof">[[expr.alignof]]</a>
 An `alignof` expression yields the alignment requirement of its operand
 type. The operand shall be a *type-id* representing a complete object
 type, or an array thereof, or a reference to one of those types.
 The result is a prvalue of type `std::size_t`.
 [*Note 1*: An `alignof` expression is an integral constant expression
-[[expr.const]]. The type `std::size_t` is defined in the standard header
-`<cstddef>` [[cstddef.syn]], [[support.types.layout]]. — *end note*]
 When `alignof` is applied to a reference type, the result is the
 alignment of the referenced type. When `alignof` is applied to an array
 type, the result is the alignment of the element type.
 #### `noexcept` operator <a id="expr.unary.noexcept">[[expr.unary.noexcept]]</a>
-The `noexcept` operator determines whether the evaluation of its
-operand, which is an unevaluated operand [[term.unevaluated.operand]],
-can throw an exception [[except.throw]].
 ``` bnf
 noexcept-expression:
   noexcept '(' expression ')'
 ```
-The result of the `noexcept` operator is a prvalue of type `bool`.
 [*Note 1*: A *noexcept-expression* is an integral constant expression
 [[expr.const]]. — *end note*]
-The result of the `noexcept` operator is `true` unless the *expression*
-is potentially-throwing [[except.spec]].
 #### New <a id="expr.new">[[expr.new]]</a>
-The *new-expression* attempts to create an object of the *type-id*
-[[dcl.name]] or *new-type-id* to which it is applied. The type of that
 object is the *allocated type*. This type shall be a complete object
 type [[term.incomplete.type]], but not an abstract class type
 [[class.abstract]] or array thereof [[intro.object]].
 [*Note 1*: Because references are not objects, references cannot be
@@ -1464,17 +1536,17 @@ noptr-new-declarator:
 new-initializer:
     '(' expression-listₒₚₜ ')'
     braced-init-list
 ```
-If a placeholder type [[dcl.spec.auto]] appears in the
-*type-specifier-seq* of a *new-type-id* or *type-id* of a
-*new-expression*, the allocated type is deduced as follows: Let *init*
-be the *new-initializer*, if any, and `T` be the *new-type-id* or
-*type-id* of the *new-expression*, then the allocated type is the type
-deduced for the variable `x` in the invented declaration
-[[dcl.spec.auto]]:
 ``` cpp
 T x init ;
 ```
@@ -1546,34 +1618,41 @@ converted constant expression [[expr.const]] of type `std::size_t` and
 its value shall be greater than zero.
 [*Example 4*: Given the definition `int n = 42`, `new float[n][5]` is
 well-formed (because `n` is the *expression* of a
 *noptr-new-declarator*), but `new float[5][n]` is ill-formed (because
-`n` is not a constant expression). — *end example*]
 If the *type-id* or *new-type-id* denotes an array type of unknown bound
 [[dcl.array]], the *new-initializer* shall not be omitted; the allocated
 object is an array with `n` elements, where `n` is determined from the
 number of initial elements supplied in the *new-initializer*
 [[dcl.init.aggr]], [[dcl.init.string]].
 If the *expression* in a *noptr-new-declarator* is present, it is
-implicitly converted to `std::size_t`. The *expression* is erroneous if:
 - the expression is of non-class type and its value before converting to
   `std::size_t` is less than zero;
 - the expression is of class type and its value before application of
-  the second standard conversion [[over.ics.user]][^23] is less than
   zero;
 - its value is such that the size of the allocated object would exceed
   the *implementation-defined* limit [[implimits]]; or
 - the *new-initializer* is a *braced-init-list* and the number of array
   elements for which initializers are provided (including the
   terminating `'\0'` in a *string-literal* [[lex.string]]) exceeds the
   number of elements to initialize.
-If the *expression* is erroneous after converting to `std::size_t`:
 - if the *expression* is a potentially-evaluated core constant
   expression, the program is ill-formed;
 - otherwise, an allocation function is not called; instead
   - if the allocation function that would have been called has a
@@ -1585,24 +1664,34 @@ If the *expression* is erroneous after converting to `std::size_t`:
     `std::bad_array_new_length` [[new.badlength]].
 When the value of the *expression* is zero, the allocation function is
 called to allocate an array with no elements.
 Objects created by a *new-expression* have dynamic storage duration
 [[basic.stc.dynamic]].
-[*Note 5*:  The lifetime of such an object is not necessarily
 restricted to the scope in which it is created. — *end note*]
 When the allocated type is “array of `N` `T`” (that is, the
 *noptr-new-declarator* syntax is used or the *new-type-id* or *type-id*
 denotes an array type), the *new-expression* yields a prvalue of type
 “pointer to `T`” that points to the initial element (if any) of the
 array. Otherwise, let `T` be the allocated type; the *new-expression* is
 a prvalue of type “pointer to T” that points to the object created.
-[*Note 6*: Both `new int` and `new int[10]` have type `int*` and the
 type of `new int[i][10]` is `int (*)[10]`. — *end note*]
 A *new-expression* may obtain storage for the object by calling an
 allocation function [[basic.stc.dynamic.allocation]]. If the
 *new-expression* terminates by throwing an exception, it may release
@@ -1611,11 +1700,11 @@ storage by calling a deallocation function
 type, the allocation function’s name is `operator new` and the
 deallocation function’s name is `operator delete`. If the allocated type
 is an array type, the allocation function’s name is `operator new[]` and
 the deallocation function’s name is `operator delete[]`.
-[*Note 7*: An implementation is required to provide default definitions
 for the global allocation functions
 [[basic.stc.dynamic]], [[new.delete.single]], [[new.delete.array]]. A
 C++ program can provide alternative definitions of these functions
 [[replacement.functions]] and/or class-specific versions [[class.free]].
 The set of allocation and deallocation functions that can be called by a
@@ -1632,16 +1721,12 @@ global scope.
 An implementation is allowed to omit a call to a replaceable global
 allocation function [[new.delete.single]], [[new.delete.array]]. When it
 does so, the storage is instead provided by the implementation or
 provided by extending the allocation of another *new-expression*.
-During an evaluation of a constant expression, a call to an allocation
-function is always omitted.
-[*Note 8*: Only *new-expression*s that would otherwise result in a call
-to a replaceable global allocation function can be evaluated in constant
-expressions [[expr.const]]. — *end note*]
 The implementation may extend the allocation of a *new-expression* `e1`
 to provide storage for a *new-expression* `e2` if the following would be
 true were the allocation not extended:
@@ -1780,13 +1865,13 @@ not be done, the deallocation function shall not be called, and the
 value of the *new-expression* shall be null.
 [*Note 11*: When the allocation function returns a value other than
 null, it must be a pointer to a block of storage in which space for the
 object has been reserved. The block of storage is assumed to be
-appropriately aligned and of the requested size. The address of the
-created object will not necessarily be the same as that of the block if
-the object is an array. — *end note*]
 A *new-expression* that creates an object of type `T` initializes that
 object as follows:
 - If the *new-initializer* is omitted, the object is default-initialized
@@ -1798,18 +1883,14 @@ object as follows:
 The invocation of the allocation function is sequenced before the
 evaluations of expressions in the *new-initializer*. Initialization of
 the allocated object is sequenced before the value computation of the
 *new-expression*.
-If the *new-expression* creates an object or an array of objects of
-class type, access and ambiguity control are done for the allocation
-function, the deallocation function [[basic.stc.dynamic.deallocation]],
-and the constructor [[class.ctor]] selected for the initialization (if
-any). If the *new-expression* creates an array of objects of class type,
-the destructor is potentially invoked [[class.dtor]].
-If any part of the object initialization described above[^24]
 terminates by throwing an exception and a suitable deallocation function
 can be found, the deallocation function is called to free the memory in
 which the object was being constructed, after which the exception
 continues to propagate in the context of the *new-expression*. If no
@@ -1834,11 +1915,13 @@ single matching deallocation function, that function will be called;
 otherwise, no deallocation function will be called. If the lookup finds
 a usual deallocation function and that function, considered as a
 placement deallocation function, would have been selected as a match for
 the allocation function, the program is ill-formed. For a non-placement
 allocation function, the normal deallocation function lookup is used to
-find the matching deallocation function [[expr.delete]].
 [*Example 7*:
 ``` cpp
 struct S {
@@ -1877,30 +1960,26 @@ delete-expression:
 ```
 The first alternative is a *single-object delete expression*, and the
 second is an *array delete expression*. Whenever the `delete` keyword is
 immediately followed by empty square brackets, it shall be interpreted
-as the second alternative.[^25]
-The operand shall be of pointer to object type or of class type. If of
-class type, the operand is contextually implicitly converted [[conv]] to
-a pointer to object type.[^26]
-The *delete-expression* has type `void`.
-If the operand has a class type, the operand is converted to a pointer
-type by calling the above-mentioned conversion function, and the
-converted operand is used in place of the original operand for the
-remainder of this subclause. In a single-object delete expression, the
-value of the operand of `delete` may be a null pointer value, a pointer
-value that resulted from a previous non-array *new-expression*, or a
-pointer to a base class subobject of an object created by such a
-*new-expression*. If not, the behavior is undefined. In an array delete
-expression, the value of the operand of `delete` may be a null pointer
-value or a pointer value that resulted from a previous array
-*new-expression* whose allocation function was not a non-allocating form
-[[new.delete.placement]].[^27]
 If not, the behavior is undefined.
 [*Note 1*: This means that the syntax of the *delete-expression* must
 match the type of the object allocated by `new`, not the syntax of the
@@ -1918,24 +1997,21 @@ delete, the static type shall be a base class of the dynamic type of the
 object to be deleted and the static type shall have a virtual destructor
 or the behavior is undefined. In an array delete expression, if the
 dynamic type of the object to be deleted is not similar to its static
 type, the behavior is undefined.
-The *cast-expression* in a *delete-expression* shall be evaluated
-exactly once.
 If the object being deleted has incomplete class type at the point of
-deletion and the complete class has a non-trivial destructor or a
-deallocation function, the behavior is undefined.
 If the value of the operand of the *delete-expression* is not a null
 pointer value and the selected deallocation function (see below) is not
-a destroying operator delete, the *delete-expression* will invoke the
-destructor (if any) for the object or the elements of the array being
-deleted. In the case of an array, the elements will be destroyed in
-order of decreasing address (that is, in reverse order of the completion
-of their constructor; see  [[class.base.init]]).
 If the value of the operand of the *delete-expression* is not a null
 pointer value, then:
 - If the allocation call for the *new-expression* for the object to be
@@ -1992,12 +2068,11 @@ declarations other than of usual deallocation functions
 [*Note 5*: If only a placement deallocation function is found in a
 class, the program is ill-formed because the lookup set is empty
 [[basic.lookup]]. — *end note*]
-If more than one deallocation function is found, the function to be
-called is selected as follows:
 - If any of the deallocation functions is a destroying operator delete,
   all deallocation functions that are not destroying operator deletes
   are eliminated from further consideration.
 - If the type has new-extended alignment, a function with a parameter of
@@ -2013,10 +2088,15 @@ called is selected as follows:
   or a (possibly multidimensional) array thereof, the function with a
   parameter of type `std::size_t` is selected.
 - Otherwise, it is unspecified whether a deallocation function with a
   parameter of type `std::size_t` is selected.
 For a single-object delete expression, the deleted object is the object
 A pointed to by the operand if the static type of A does not have a
 virtual destructor, and the most-derived object of A otherwise.
 [*Note 6*: If the deallocation function is not a destroying operator
@@ -2047,12 +2127,181 @@ passed as the corresponding argument.
 function, and either the first argument was not the result of a prior
 call to a replaceable allocation function or the second or third
 argument was not the corresponding argument in said call, the behavior
 is undefined [[new.delete.single]], [[new.delete.array]]. — *end note*]
-Access and ambiguity control are done for both the deallocation function
-and the destructor [[class.dtor]], [[class.free]].
 ### Explicit type conversion (cast notation) <a id="expr.cast">[[expr.cast]]</a>
 The result of the expression `(T)` *cast-expression* is of type `T`. The
 result is an lvalue if `T` is an lvalue reference type or an rvalue
@@ -2102,12 +2351,13 @@ conversion is valid even if the base class is inaccessible:
   of a derived class type, respectively.
 If a conversion can be interpreted in more than one of the ways listed
 above, the interpretation that appears first in the list is used, even
 if a cast resulting from that interpretation is ill-formed. If a
-conversion can be interpreted in more than one way as a `static_cast`
-followed by a `const_cast`, the conversion is ill-formed.
 [*Example 1*:
 ``` cpp
 struct A { };
@@ -2115,10 +2365,19 @@ struct I1 : A { };
 struct I2 : A { };
 struct D : I1, I2 { };
 A* foo( D* p ) {
   return (A*)( p );             // ill-formed static_cast interpretation
 }
 ```
 — *end example*]
 The operand of a cast using the cast notation can be a prvalue of type
@@ -2128,13 +2387,13 @@ operand and destination types are class types and one or both are
 incomplete, it is unspecified whether the `static_cast` or the
 `reinterpret_cast` interpretation is used, even if there is an
 inheritance relationship between the two classes.
 [*Note 2*: For example, if the classes were defined later in the
-translation unit, a multi-pass compiler would be permitted to interpret
-a cast between pointers to the classes as if the class types were
-complete at the point of the cast. — *end note*]
 ### Pointer-to-member operators <a id="expr.mptr.oper">[[expr.mptr.oper]]</a>
 The pointer-to-member operators `->*` and `.*` group left-to-right.
@@ -2143,21 +2402,21 @@ pm-expression:
     cast-expression
     pm-expression '.*' cast-expression
     pm-expression '->*' cast-expression
 ```
-The binary operator `.*` binds its second operand, which shall be of
-type “pointer to member of `T`” to its first operand, which shall be a
-glvalue of class `T` or of a class of which `T` is an unambiguous and
-accessible base class. The result is an object or a function of the type
-specified by the second operand.
-The binary operator `->*` binds its second operand, which shall be of
-type “pointer to member of `T`” to its first operand, which shall be of
-type “pointer to `U`” where `U` is either `T` or a class of which `T` is
-an unambiguous and accessible base class. The expression `E1->*E2` is
-converted into the equivalent form `(*(E1)).*E2`.
 Abbreviating *pm-expression*`.*`*cast-expression* as `E1.*E2`, `E1` is
 called the *object expression*. If the result of `E1` is an object whose
 type is not similar to the type of `E1`, or whose most derived object
 does not contain the member to which `E2` refers, the behavior is
@@ -2233,77 +2492,80 @@ are performed on the operands and determine the type of the result.
 The binary `*` operator indicates multiplication.
 The binary `/` operator yields the quotient, and the binary `%` operator
 yields the remainder from the division of the first expression by the
-second. If the second operand of `/` or `%` is zero the behavior is
-undefined. For integral operands the `/` operator yields the algebraic
-quotient with any fractional part discarded;[^28]
 if the quotient `a/b` is representable in the type of the result,
 `(a/b)*b + a%b` is equal to `a`; otherwise, the behavior of both `a/b`
 and `a%b` is undefined.
 ### Additive operators <a id="expr.add">[[expr.add]]</a>
-The additive operators `+` and `-` group left-to-right. The usual
-arithmetic conversions [[expr.arith.conv]] are performed for operands of
-arithmetic or enumeration type.
 ``` bnf
 additive-expression:
     multiplicative-expression
     additive-expression '+' multiplicative-expression
     additive-expression '-' multiplicative-expression
 ```
-For addition, either both operands shall have arithmetic or unscoped
-enumeration type, or one operand shall be a pointer to a
-completely-defined object type and the other shall have integral or
-unscoped enumeration type.
 For subtraction, one of the following shall hold:
-- both operands have arithmetic or unscoped enumeration type; or
 - both operands are pointers to cv-qualified or cv-unqualified versions
   of the same completely-defined object type; or
 - the left operand is a pointer to a completely-defined object type and
-  the right operand has integral or unscoped enumeration type.
 The result of the binary `+` operator is the sum of the operands. The
 result of the binary `-` operator is the difference resulting from the
 subtraction of the second operand from the first.
 When an expression `J` that has integral type is added to or subtracted
 from an expression `P` of pointer type, the result has the type of `P`.
 - If `P` evaluates to a null pointer value and `J` evaluates to 0, the
   result is a null pointer value.
-- Otherwise, if `P` points to an array element i of an array object `x`
-  with n elements [[dcl.array]],[^29] the expressions `P + J` and
-  `J + P` (where `J` has the value j) point to the
-  (possibly-hypothetical) array element i + j of `x` if 0 ≤ i + j ≤ n
-  and the expression `P - J` points to the (possibly-hypothetical) array
-  element i - j of `x` if 0 ≤ i - j ≤ n.
 - Otherwise, the behavior is undefined.
 [*Note 1*: Adding a value other than 0 or 1 to a pointer to a base
 class subobject, a member subobject, or a complete object results in
 undefined behavior. — *end note*]
 When two pointer expressions `P` and `Q` are subtracted, the type of the
 result is an *implementation-defined* signed integral type; this type
-shall be the same type that is defined as `std::ptrdiff_t` in the
 `<cstddef>` header [[support.types.layout]].
 - If `P` and `Q` both evaluate to null pointer values, the result is 0.
 - Otherwise, if `P` and `Q` point to, respectively, array elements i and
   j of the same array object `x`, the expression `P - Q` has the value
-  i - j.
-- Otherwise, the behavior is undefined. \[*Note 2*: If the value i - j
- is not in the range of representable values of type `std::ptrdiff_t`,
- the behavior is undefined. — *end note*]
 For addition or subtraction, if the expressions `P` or `Q` have type
 “pointer to cv `T`”, where `T` and the array element type are not
 similar [[conv.qual]], the behavior is undefined.
@@ -2327,23 +2589,24 @@ shift-expression:
     additive-expression
     shift-expression '<<' additive-expression
     shift-expression '>>' additive-expression
 ```
-The operands shall be of integral or unscoped enumeration type and
-integral promotions are performed. The type of the result is that of the
-promoted left operand. The behavior is undefined if the right operand is
-negative, or greater than or equal to the width of the promoted left
-operand.
 The value of `E1 << E2` is the unique value congruent to `E1` × 2^`E2`
 modulo 2ᴺ, where N is the width of the type of the result.
 [*Note 1*: `E1` is left-shifted `E2` bit positions; vacated bits are
 zero-filled. — *end note*]
-The value of `E1 >> E2` is `E1` / 2^`E2`, rounded down.
 [*Note 2*: `E1` is right-shifted `E2` bit positions. Right-shift on
 signed integral types is an arithmetic right shift, which performs
 sign-extension. — *end note*]
@@ -2436,28 +2699,28 @@ relational-expression:
     relational-expression '>' compare-expression
     relational-expression '<=' compare-expression
     relational-expression '>=' compare-expression
 ```
-The lvalue-to-rvalue [[conv.lval]], array-to-pointer [[conv.array]], and
-function-to-pointer [[conv.func]] standard conversions are performed on
-the operands. The comparison is deprecated if both operands were of
-array type prior to these conversions [[depr.array.comp]].
 The converted operands shall have arithmetic, enumeration, or pointer
 type. The operators `<` (less than), `>` (greater than), `<=` (less than
 or equal to), and `>=` (greater than or equal to) all yield `false` or
 `true`. The type of the result is `bool`.
 The usual arithmetic conversions [[expr.arith.conv]] are performed on
-operands of arithmetic or enumeration type. If both operands are
-pointers, pointer conversions [[conv.ptr]] and qualification conversions
-[[conv.qual]] are performed to bring them to their composite pointer
-type [[expr.type]]. After conversions, the operands shall have the same
-type.
-The result of comparing unequal pointers to objects[^30]
 is defined in terms of a partial order consistent with the following
 rules:
 - If two pointers point to different elements of the same array, or to
@@ -2477,12 +2740,12 @@ a pointer to object `p` compares greater than a pointer `q`, `p>=q`,
 `p>q`, `q<=p`, and `q<p` all yield `true` and `p<=q`, `p<q`, `q>=p`, and
 `q>p` all yield `false`. Otherwise, the result of each of the operators
 is unspecified.
 [*Note 1*: A relational operator applied to unequal function pointers
-or to unequal pointers to `void` yields an unspecified
-result. — *end note*]
 If both operands (after conversions) are of arithmetic or enumeration
 type, each of the operators shall yield `true` if the specified
 relationship is true and `false` if it is false.
@@ -2494,31 +2757,30 @@ equality-expression:
     equality-expression '==' relational-expression
     equality-expression '!=' relational-expression
 ```
 The `==` (equal to) and the `!=` (not equal to) operators group
-left-to-right. The lvalue-to-rvalue [[conv.lval]], array-to-pointer
-[[conv.array]], and function-to-pointer [[conv.func]] standard
-conversions are performed on the operands. The comparison is deprecated
-if both operands were of array type prior to these conversions
-[[depr.array.comp]].
-The converted operands shall have arithmetic, enumeration, pointer, or
-pointer-to-member type, or type `std::nullptr_t`. The operators `==` and
 `!=` both yield `true` or `false`, i.e., a result of type `bool`. In
 each case below, the operands shall have the same type after the
 specified conversions have been applied.
-If at least one of the operands is a pointer, pointer conversions
-[[conv.ptr]], function pointer conversions [[conv.fctptr]], and
-qualification conversions [[conv.qual]] are performed on both operands
-to bring them to their composite pointer type [[expr.type]]. Comparing
-pointers is defined as follows:
 - If one pointer represents the address of a complete object, and
   another pointer represents the address one past the last element of a
-  different complete object,[^31] the result of the comparison is
   unspecified.
 - Otherwise, if the pointers are both null, both point to the same
   function, or both represent the same address [[basic.compound]], they
   compare equal.
 - Otherwise, the pointers compare unequal.
@@ -2578,10 +2840,23 @@ performed on both operands to bring them to their composite pointer type
   — *end example*]
 Two operands of type `std::nullptr_t` or one operand of type
 `std::nullptr_t` and the other a null pointer constant compare equal.
 If two operands compare equal, the result is `true` for the `==`
 operator and `false` for the `!=` operator. If two operands compare
 unequal, the result is `false` for the `==` operator and `true` for the
 `!=` operator. Otherwise, the result of each of the operators is
 unspecified.
@@ -2736,33 +3011,36 @@ type `T2` of the operand expression `E2` as follows:
   but an implicit conversion sequence can only be formed if the
   reference would bind directly.
 - If `E2` is a prvalue or if neither of the conversion sequences above
   can be formed and at least one of the operands has (possibly
   cv-qualified) class type:
-  - if `T1` and `T2` are the same class type (ignoring cv-qualification)
- and `T2` is at least as cv-qualified as `T1`, the target type is
       `T2`,
   - otherwise, if `T2` is a base class of `T1`, the target type is *cv1*
-    `T2`, where *cv1* denotes the cv-qualifiers of `T1`,
   - otherwise, the target type is the type that `E2` would have after
     applying the lvalue-to-rvalue [[conv.lval]], array-to-pointer
     [[conv.array]], and function-to-pointer [[conv.func]] standard
     conversions.
 Using this process, it is determined whether an implicit conversion
 sequence can be formed from the second operand to the target type
-determined for the third operand, and vice versa. If both sequences can
-be formed, or one can be formed but it is the ambiguous conversion
-sequence, the program is ill-formed. If no conversion sequence can be
-formed, the operands are left unchanged and further checking is
-performed as described below. Otherwise, if exactly one conversion
-sequence can be formed, that conversion is applied to the chosen operand
-and the converted operand is used in place of the original operand for
-the remainder of this subclause.
-[*Note 3*: The conversion might be ill-formed even if an implicit
-conversion sequence could be formed. — *end note*]
 If the second and third operands are glvalues of the same value category
 and have the same type, the result is of that type and value category
 and it is a bit-field if the second or the third operand is a bit-field,
 or if both are bit-fields.
@@ -2774,41 +3052,40 @@ to be applied to the operands [[over.match.oper]], [[over.built]]. If
 the overload resolution fails, the program is ill-formed. Otherwise, the
 conversions thus determined are applied, and the converted operands are
 used in place of the original operands for the remainder of this
 subclause.
-Lvalue-to-rvalue [[conv.lval]], array-to-pointer [[conv.array]], and
-function-to-pointer [[conv.func]] standard conversions are performed on
-the second and third operands. After those conversions, one of the
-following shall hold:
 - The second and third operands have the same type; the result is of
-  that type and the result object is initialized using the selected
   operand.
 - The second and third operands have arithmetic or enumeration type; the
   usual arithmetic conversions [[expr.arith.conv]] are performed to
   bring them to a common type, and the result is of that type.
 - One or both of the second and third operands have pointer type;
- pointer conversions [[conv.ptr]], function pointer conversions
   [[conv.fctptr]], and qualification conversions [[conv.qual]] are
   performed to bring them to their composite pointer type [[expr.type]].
   The result is of the composite pointer type.
 - One or both of the second and third operands have pointer-to-member
-  type; pointer to member conversions [[conv.mem]], function pointer
- conversions [[conv.fctptr]], and qualification conversions
   [[conv.qual]] are performed to bring them to their composite pointer
   type [[expr.type]]. The result is of the composite pointer type.
 - Both the second and third operands have type `std::nullptr_t` or one
   has that type and the other is a null pointer constant. The result is
   of type `std::nullptr_t`.
 ### Yielding a value <a id="expr.yield">[[expr.yield]]</a>
 ``` bnf
 yield-expression:
- 'co_yield' assignment-expression
- 'co_yield' braced-init-list
 ```
 A *yield-expression* shall appear only within a suspension context of a
 function [[expr.await]]. Let *e* be the operand of the
 *yield-expression* and *p* be an lvalue naming the promise object of the
@@ -2860,20 +3137,24 @@ throw-expression:
     throw assignment-expressionₒₚₜ
 ```
 A *throw-expression* is of type `void`.
-Evaluating a *throw-expression* with an operand throws an exception
-[[except.throw]]; the type of the exception object is determined by
-removing any top-level *cv-qualifier*s from the static type of the
-operand and adjusting the type from “array of `T`” or function type `T`
-to “pointer to `T`”.
 A *throw-expression* with no operand rethrows the currently handled
-exception [[except.handle]]. The exception is reactivated with the
-existing exception object; no new exception object is created. The
-exception is no longer considered to be caught.
 [*Example 1*:
 An exception handler that cannot completely handle the exception itself
 can be written like this:
@@ -2887,15 +3168,11 @@ try {
 }
 ```
 — *end example*]
-If no exception is presently being handled, evaluating a
-*throw-expression* with no operand calls `std::{}terminate()`
-[[except.terminate]].
-### Assignment and compound assignment operators <a id="expr.ass">[[expr.ass]]</a>
 The assignment operator (`=`) and the compound assignment operators all
 group right-to-left. All require a modifiable lvalue as their left
 operand; their result is an lvalue of the type of the left operand,
 referring to the left operand. The result in all cases is a bit-field if
@@ -2921,13 +3198,14 @@ assignment-expression:
 ``` bnf
 assignment-operator: one of
     '= *= /= %= += -= >>= <<= &= ^= |='
 ```
-In simple assignment (`=`), the object referred to by the left operand
-is modified [[defns.access]] by replacing its value with the result of
-the right operand.
 If the right operand is an expression, it is implicitly converted
 [[conv]] to the cv-unqualified type of the left operand.
 When the left operand of an assignment operator is a bit-field that
@@ -2957,19 +3235,18 @@ the behavior is undefined.
 [*Note 3*: This restriction applies to the relationship between the
 left and right sides of the assignment operation; it is not a statement
 about how the target of the assignment can be aliased in general. See
 [[basic.lval]]. — *end note*]
-A *braced-init-list* may appear on the right-hand side of
-- an assignment to a scalar, in which case the initializer list shall
- have at most a single element. The meaning of `x = {v}`, where `T` is
- the scalar type of the expression `x`, is that of `x = T{v}`. The
-  meaning of `x = {}` is `x = T{}`.
-- an assignment to an object of class type, in which case the
- initializer list is passed as the argument to the assignment operator
-  function selected by overload resolution [[over.ass]], [[over.match]].
 [*Example 1*:
 ``` cpp
 complex<double> z;

     postfix-expression '(' expression-listₒₚₜ ')'
     simple-type-specifier '(' expression-listₒₚₜ ')'
     typename-specifier '(' expression-listₒₚₜ ')'
     simple-type-specifier braced-init-list
     typename-specifier braced-init-list
+    postfix-expression '.' templateₒₚₜ id-expression
+    postfix-expression '.' splice-expression
+    postfix-expression '->' templateₒₚₜ id-expression
+    postfix-expression '->' splice-expression
     postfix-expression '++'
     postfix-expression '--'
     dynamic_cast '<' type-id '>' '(' expression ')'
     static_cast '<' type-id '>' '(' expression ')'
     reinterpret_cast '<' type-id '>' '(' expression ')'
 A *subscript expression* is a postfix expression followed by square
 brackets containing a possibly empty, comma-separated list of
 *initializer-clause*s that constitute the arguments to the subscript
 operator. The *postfix-expression* and the initialization of the object
+parameter [[dcl.fct]] of any applicable subscript operator function
+[[over.sub]] is sequenced before each expression in the
+*expression-list* and also before any default argument
+[[dcl.fct.default]]. The initialization of a non-object parameter of a
+subscript operator function `S`, including every associated value
+computation and side effect, is indeterminately sequenced with respect
+to that of any other non-object parameter of `S`.
 With the built-in subscript operator, an *expression-list* shall be
 present, consisting of a single *assignment-expression*. One of the
 expressions shall be a glvalue of type “array of `T`” or a prvalue of
 type “pointer to `T`” and the other shall be a prvalue of unscoped
 enumeration or integral type. The result is of type “`T`”. The type
+“`T`” shall be a completely-defined object type.[^10]
 The expression `E1[E2]` is identical (by definition) to `*((E1)+(E2))`,
 except that in the case of an array operand, the result is an lvalue if
 that operand is an lvalue and an xvalue otherwise.
 A function call is a postfix expression followed by parentheses
 containing a possibly empty, comma-separated list of
 *initializer-clause*s which constitute the arguments to the function.
+[*Note 1*: If the postfix expression is a function name, the
+appropriate function and the validity of the call are determined
+according to the rules in  [[over.match]]. — *end note*]
 The postfix expression shall have function type or function pointer
 type. For a call to a non-member function or to a static member
+function, the postfix expression shall be either an lvalue that refers
 to a function (in which case the function-to-pointer standard conversion
+[[conv.func]] is suppressed on the postfix expression), or a prvalue of
+function pointer type.
 If the selected function is non-virtual, or if the *id-expression* in
 the class member access expression is a *qualified-id*, that function is
 called. Otherwise, its final overrider [[class.virtual]] in the dynamic
 type of the object expression is called; such a call is referred to as a
 [*Note 2*: The dynamic type is the type of the object referred to by
 the current value of the object expression. [[class.cdtor]] describes
 the behavior of virtual function calls when the object expression refers
 to an object under construction or destruction. — *end note*]
+[*Note 3*: If a function name is used, and name lookup [[basic.lookup]]
+does not find a declaration of that name, the program is ill-formed. No
+function is implicitly declared by such a call. — *end note*]
 If the *postfix-expression* names a destructor or pseudo-destructor
 [[expr.prim.id.dtor]], the type of the function call expression is
 `void`; otherwise, the type of the function call expression is the
 return type of the statically chosen function (i.e., ignoring the
 which case the *postfix-expression* is a possibly-parenthesized class
 member access), the function call destroys the object of scalar type
 denoted by the object expression of the class member access
 [[expr.ref]], [[basic.life]].
+A type `T`_call is *call-compatible* with a function type `T`_func if
+`T`_call is the same type as `T`_func or if the type “pointer to
+`T`_func” can be converted to type “pointer to `T`_call” via a function
+pointer conversion [[conv.fctptr]]. Calling a function through an
+expression whose function type is not call-compatible with the type of
+the called function’s definition results in undefined behavior.
+[*Note 4*: This requirement allows the case when the expression has the
+type of a potentially-throwing function, but the called function has a
 non-throwing exception specification, and the function types are
 otherwise the same. — *end note*]
 When a function is called, each parameter [[dcl.fct]] is initialized
+[[dcl.init]], [[class.copy.ctor]] with its corresponding argument, and
+each precondition assertion of the function is evaluated
+[[dcl.contract.func]]. If the function is an explicit object member
+function and there is an implied object argument [[over.call.func]], the
+list of provided arguments is preceded by the implied object argument
+for the purposes of this correspondence. If there is no corresponding
+argument, the default argument for the parameter is used.
 [*Example 1*:
 ``` cpp
 template<typename ...T> int f(int n = 0, T ...t);
 int x = f<int>();               // error: no argument for second function parameter
 ```
 — *end example*]
+If the function is an implicit object member function, the object
+expression of the class member access shall be a glvalue and the
+implicit object parameter of the function [[over.match.funcs]] is
+initialized with that glvalue, converted as if by an explicit type
 conversion [[expr.cast]].
 [*Note 5*: There is no access or ambiguity checking on this conversion;
 the access checking and disambiguation are done as part of the (possibly
 implicit) class member access operator. See  [[class.member.lookup]],
 [*Note 6*: This still allows a parameter to be a pointer or reference
 to such a type. However, it prevents a passed-by-value parameter to have
 an incomplete or abstract class type. — *end note*]
+It is *implementation-defined* whether a parameter is destroyed when the
+function in which it is defined exits
+[[stmt.return]], [[except.ctor]], [[expr.await]] or at the end of the
+enclosing full-expression; parameters are always destroyed in the
+reverse order of their construction. The initialization and destruction
+of each parameter occurs within the context of the full-expression
+[[intro.execution]] where the function call appears.
+[*Example 2*: The access [[class.access.general]] of the constructor,
+conversion functions, or destructor is checked at the point of call. If
+a constructor or destructor for a function parameter throws an
+exception, any *function-try-block* [[except.pre]] of the called
+function with a handler that can handle the exception is not
 considered. — *end example*]
 The *postfix-expression* is sequenced before each *expression* in the
 *expression-list* and any default argument. The initialization of a
+parameter or, if the implementation introduces any temporary objects to
+hold the values of function parameters [[class.temporary]], the
+initialization of those temporaries, including every associated value
+computation and side effect, is indeterminately sequenced with respect
+to that of any other parameter. These evaluations are sequenced before
+the evaluation of the precondition assertions of the function, which are
+evaluated in sequence [[dcl.contract.func]]. For any temporaries
+introduced to hold the values of function parameters, the initialization
+of the parameter objects from those temporaries is indeterminately
+sequenced with respect to the evaluation of each precondition assertion.
 [*Note 7*: All side effects of argument evaluations are sequenced
 before the function is entered (see
 [[intro.execution]]). — *end note*]
 function call if the return type of the final overrider is different
 from the return type of the statically chosen function, the value
 returned from the final overrider is converted to the return type of the
 statically chosen function.
+When the called function exits normally [[stmt.return]], [[expr.await]],
+all postcondition assertions of the function are evaluated in sequence
+[[dcl.contract.func]]. If the implementation introduces any temporary
+objects to hold the result value as specified in [[class.temporary]],
+the evaluation of each postcondition assertion is indeterminately
+sequenced with respect to the initialization of any of those temporaries
+or the result object. These evaluations, in turn, are sequenced before
+the destruction of any function parameters.
 [*Note 9*:  A function can change the values of its non-const
 parameters, but these changes cannot affect the values of the arguments
 except where a parameter is of a reference type [[dcl.ref]]; if the
+reference is to a const-qualified type, `const_cast` needs to be used to
+cast away the constness in order to modify the argument’s value. Where a
+parameter is of `const` reference type a temporary object is introduced
+if needed
 [[dcl.type]], [[lex.literal]], [[lex.string]], [[dcl.array]], [[class.temporary]].
 In addition, it is possible to modify the values of non-constant objects
 through pointer parameters. — *end note*]
 A function can be declared to accept fewer arguments (by declaring
 function-to-pointer [[conv.func]] standard conversions are performed on
 the argument expression. An argument that has type cv `std::nullptr_t`
 is converted to type `void*` [[conv.ptr]]. After these conversions, if
 the argument does not have arithmetic, enumeration, pointer,
 pointer-to-member, or class type, the program is ill-formed. Passing a
+potentially-evaluated argument of a scoped enumeration type [[dcl.enum]]
+or of a class type [[class]] having an eligible non-trivial copy
+constructor [[special]], [[class.copy.ctor]], an eligible non-trivial
+move constructor, or a non-trivial destructor [[class.dtor]], with no
+corresponding parameter, is conditionally-supported with
+*implementation-defined* semantics. If the argument has integral or
 enumeration type that is subject to the integral promotions
 [[conv.prom]], or a floating-point type that is subject to the
 floating-point promotion [[conv.fpprom]], the value of the argument is
 converted to the promoted type before the call. These promotions are
 referred to as the *default argument promotions*.
 Recursive calls are permitted, except to the `main` function
 [[basic.start.main]].
 A function call is an lvalue if the result type is an lvalue reference
 type or an rvalue reference to function type, an xvalue if the result
+type is an rvalue reference to object type, and a prvalue otherwise. If
+it is a non-void prvalue, the type of the function call expression shall
+be complete, except as specified in [[dcl.type.decltype]].
 #### Explicit type conversion (functional notation) <a id="expr.type.conv">[[expr.type.conv]]</a>
 A *simple-type-specifier* [[dcl.type.simple]] or *typename-specifier*
 [[temp.res]] followed by a parenthesized optional *expression-list* or
 deduced class type, it is replaced by the return type of the function
 selected by overload resolution for class template deduction
 [[over.match.class.deduct]] for the remainder of this subclause.
 Otherwise, if the type contains a placeholder type, it is replaced by
 the type determined by placeholder type deduction
+[[dcl.type.auto.deduct]]. Let `T` denote the resulting type. Then:
+- If the initializer is a parenthesized single expression, the type
+  conversion expression is equivalent to the corresponding cast
+  expression [[expr.cast]].
+- Otherwise, if `T` is cv `void`, the initializer shall be `()` or `{}`
+  (after pack expansion, if any), and the expression is a prvalue of
+  type `void` that performs no initialization.
+- Otherwise, if `T` is a reference type, the expression has the same
+  effect as direct-initializing an invented variable `t` of type `T`
+  from the initializer and then using `t` as the result of the
+  expression; the result is an lvalue if `T` is an lvalue reference type
+  or an rvalue reference to function type and an xvalue otherwise.
+- Otherwise, the expression is a prvalue of type `T` whose result object
+  is direct-initialized [[dcl.init]] with the initializer.
+If the initializer is a parenthesized optional *expression-list*, `T`
+shall not be an array type.
 [*Example 1*:
 ``` cpp
 struct A {};
 }
 ```
 — *end example*]
 #### Class member access <a id="expr.ref">[[expr.ref]]</a>
 A postfix expression followed by a dot `.` or an arrow `->`, optionally
 followed by the keyword `template`, and then followed by an
+*id-expression* or a *splice-expression*, is a postfix expression.
+[*Note 1*: If the keyword `template` is used and followed by an
+*id-expression*, the unqualified name is considered to refer to a
+template [[temp.names]]. If a *simple-template-id* results and is
+followed by a `::`, the *id-expression* is a
+*qualified-id*. — *end note*]
+For a dot that is followed by an expression that designates a static
+member or an enumerator, the first expression is a discarded-value
+expression [[expr.context]]; if the expression after the dot designates
+a non-static data member, the first expression shall be a glvalue. A
+postfix expression that is followed by an arrow shall be a prvalue
+having pointer type. The expression `E1->E2` is converted to the
+equivalent form `(*(E1)).E2`; the remainder of [[expr.ref]] will address
+only the form using a dot.[^11]
+The postfix expression before the dot is evaluated;[^12]
+the result of that evaluation, together with the *id-expression* or
+*splice-expression*, determines the result of the entire postfix
+expression.
+Abbreviating *postfix-expression*`.`*id-expression* or
+*postfix-expression*`.`*splice-expression* as `E1.E2`, `E1` is called
+the *object expression*. If the object expression is of scalar type,
+`E2` shall name the pseudo-destructor of that same type (ignoring
 cv-qualifications) and `E1.E2` is a prvalue of type “function of ()
 returning `void`”.
 [*Note 2*: This value can only be used for a notional function call
 [[expr.prim.id.dtor]]. — *end note*]
 when the class is complete [[class.member.lookup]]. — *end note*]
 [*Note 4*:  [[basic.lookup.qual]] describes how names are looked up
 after the `.` and `->` operators. — *end note*]
+If `E2` is a *splice-expression*, then let `T1` be the type of `E1`.
+`E2` shall designate either a member of `T1` or a direct base class
+relationship (`T1`, `B`).
+If `E2` designates a bit-field, `E1.E2` is a bit-field. The type and
+value category of `E1.E2` are determined as follows. In the remainder
+of  [[expr.ref]], *cq* represents either `const` or the absence of
+`const` and *vq* represents either `volatile` or the absence of
+`volatile`. *cv* represents an arbitrary set of cv-qualifiers, as
+defined in  [[basic.type.qualifier]].
+If `E2` designates an entity that is declared to have type “reference to
+`T`”, then `E1.E2` is an lvalue of type `T`. In that case, if `E2`
+designates a static data member, `E1.E2` designates the object or
+function to which the reference is bound, otherwise `E1.E2` designates
+the object or function to which the corresponding reference member of
+`E1` is bound. Otherwise, one of the following rules applies.
+- If `E2` designates a static data member and the type of `E2` is `T`,
+ then `E1.E2` is an lvalue; the expression designates the named member
+ of the class. The type of `E1.E2` is `T`.
+- Otherwise, if `E2` designates a non-static data member and the type of
+  `E1` is “*cq1 vq1* `X`”, and the type of `E2` is “*cq2 vq2* `T`”, the
+ expression designates the corresponding member subobject of the object
+ designated by `E1`. If `E1` is an lvalue, then `E1.E2` is an lvalue;
+ otherwise `E1.E2` is an xvalue. Let the notation *vq12* stand for the
+  “union” of *vq1* and *vq2*; that is, if *vq1* or *vq2* is `volatile`,
+ then *vq12* is `volatile`. Similarly, let the notation *cq12* stand
+ for the “union” of *cq1* and *cq2*; that is, if *cq1* or *cq2* is
+ `const`, then *cq12* is `const`. If the entity designated by `E2` is
+  declared to be a `mutable` member, then the type of `E1.E2` is “*vq12*
+  `T`”. If the entity designated by `E2` is not declared to be a
+  `mutable` member, then the type of `E1.E2` is “*cq12* *vq12* `T`”.
+- Otherwise, if `E2` denotes an overload set, the expression shall be
+  the (possibly-parenthesized) left-hand operand of a member function
+  call [[expr.call]], and function overload resolution [[over.match]] is
+  used to select the function to which `E2` refers. The type of `E1.E2`
+  is the type of `E2` and `E1.E2` refers to the function referred to by
+  `E2`.
   - If `E2` refers to a static member function, `E1.E2` is an lvalue.
   - Otherwise (when `E2` refers to a non-static member function),
+    `E1.E2` is a prvalue. \[*Note 5*: Any redundant set of parentheses
+ surrounding the expression is ignored
+    [[expr.prim.paren]]. — *end note*]
+- Otherwise, if `E2` designates a nested type, the expression `E1.E2` is
+ ill-formed.
+- Otherwise, if `E2` designates a member enumerator and the type of `E2`
+ is `T`, the expression `E1.E2` is a prvalue of type `T` whose value is
+ the value of the enumerator.
+- Otherwise, if `E2` designates a direct base class relationship (D, B)
+  and the type of `E1` is cv `T`, the expression designates the direct
+  base class subobject of type B of the object designated by `E1`. If
+  `E1` is an lvalue, then `E1.E2` is an lvalue; otherwise, `E1.E2` is an
+  xvalue. The type of `E1.E2` is “cv `B`”.
+  \[*Note 6*: This can only occur in an expression of the form
+  `e1.[:e2:]`. — *end note*]
+  \[*Example 1*:
+  ``` cpp
+  struct B {
+    int b;
+  };
+  struct C : B {
+    int get() const { return b; }
+  };
+  struct D : B, C { };
+  constexpr int f() {
+    D d = {1, {}};
+    // b unambiguously refers to the direct base class of type B,
+    // not the indirect base class of type B
+    B& b = d.[: std::meta::bases_of(^^D, std::meta::access_context::current())[0] :];
+    b.b += 10;
+    return 10 * b.b + d.get();
+  }
+  static_assert(f() == 110);
+  ```
+  — *end example*]
+- Otherwise, the program is ill-formed.
+If `E2` designates a non-static member (possibly after overload
+resolution), the program is ill-formed if the class of which `E2`
+designates a direct member is an ambiguous base [[class.member.lookup]]
+of the designating class [[class.access.base]] of `E2`.
+[*Note 7*: The program is also ill-formed if the naming class is an
 ambiguous base of the class type of the object expression; see
 [[class.access.base]]. — *end note*]
+If `E2` designates a non-static member (possibly after overload
+resolution) and the result of `E1` is an object whose type is not
+similar [[conv.qual]] to the type of `E1`, the behavior is undefined.
+[*Example 2*:
 ``` cpp
 struct A { int i; };
 struct B { int j; };
 struct D : A, B {};
 — *end example*]
 #### Increment and decrement <a id="expr.post.incr">[[expr.post.incr]]</a>
+The value of a postfix `++` expression is the value obtained by applying
+the lvalue-to-rvalue conversion [[conv.lval]] to its operand.
 [*Note 1*: The value obtained is a copy of the original
 value. — *end note*]
 The operand shall be a modifiable lvalue. The type of the operand shall
 be an arithmetic type other than cv `bool`, or a pointer to a complete
 object type. An operand with volatile-qualified type is deprecated; see
 [[depr.volatile.type]]. The value of the operand object is modified
+[[defns.access]] as if it were the operand of the prefix `++` operator
+[[expr.pre.incr]]. The value computation of the `++` expression is
+sequenced before the modification of the operand object. With respect to
+an indeterminately-sequenced function call, the operation of postfix
+`++` is a single evaluation.
 [*Note 2*: Therefore, a function call cannot intervene between the
 lvalue-to-rvalue conversion and the side effect associated with any
 single postfix `++` operator. — *end note*]
 The result is a prvalue. The type of the result is the cv-unqualified
+version of the type of the operand.
 The operand of postfix `--` is decremented analogously to the postfix
 `++` operator.
 [*Note 3*: For prefix increment and decrement, see
 such that `B` is a base class of `D`, the result is a pointer to the
 unique `B` subobject of the `D` object pointed to by `v`, or a null
 pointer value if `v` is a null pointer value. Similarly, if `T` is
 “reference to *cv1* `B`” and `v` has type *cv2* `D` such that `B` is a
 base class of `D`, the result is the unique `B` subobject of the `D`
+object referred to by `v`.[^13]
 In both the pointer and reference cases, the program is ill-formed if
 `B` is an inaccessible or ambiguous base class of `D`.
 [*Example 1*:
 Otherwise, `v` shall be a pointer to or a glvalue of a polymorphic type
 [[class.virtual]].
 If `v` is a null pointer value, the result is a null pointer value.
+If `v` has type “pointer to cv `U`” and `v` does not point to an object
+whose type is similar [[conv.qual]] to `U` and that is within its
+lifetime or within its period of construction or destruction
+[[class.cdtor]], the behavior is undefined. If `v` is a glvalue of type
+`U` and `v` does not refer to an object whose type is similar to `U` and
+that is within its lifetime or within its period of construction or
+destruction, the behavior is undefined.
 If `T` is “pointer to cv `void`”, then the result is a pointer to the
 most derived object pointed to by `v`. Otherwise, a runtime check is
 applied to see if the object pointed or referred to by `v` can be
 converted to the type pointed or referred to by `T`.
 check logically executes as follows:
 - If, in the most derived object pointed (referred) to by `v`, `v`
   points (refers) to a public base class subobject of a `C` object, and
   if only one object of type `C` is derived from the subobject pointed
+  (referred) to by `v`, the result points (refers) to that `C` object.
 - Otherwise, if `v` points (refers) to a public base class subobject of
   the most derived object, and the type of the most derived object has a
   base class, of type `C`, that is unambiguous and public, the result
   points (refers) to the `C` subobject of the most derived object.
 - Otherwise, the runtime check *fails*.
 #### Type identification <a id="expr.typeid">[[expr.typeid]]</a>
 The result of a `typeid` expression is an lvalue of static type `const`
 `std::type_info` [[type.info]] and dynamic type `const` `std::type_info`
+or `const` `name` where `name` is an *implementation-defined* class
 publicly derived from `std::type_info` which preserves the behavior
+described in  [[type.info]].[^14]
 The lifetime of the object referred to by the lvalue extends to the end
 of the program. Whether or not the destructor is called for the
 `std::type_info` object at the end of the program is unspecified.
 If the type of the *expression* or *type-id* operand is a (possibly
 cv-qualified) class type or a reference to (possibly cv-qualified) class
 type, that class shall be completely defined.
+If an *expression* operand of `typeid` is a possibly-parenthesized
+*unary-expression* whose *unary-operator* is `*` and whose operand
+evaluates to a null pointer value [[basic.compound]], the `typeid`
+expression throws an exception [[except.throw]] of a type that would
+match a handler of type `std::bad_typeid` [[bad.typeid]].
+[*Note 1*: In other contexts, evaluating such a *unary-expression*
+results in undefined behavior [[expr.unary.op]]. — *end note*]
 When `typeid` is applied to a glvalue whose type is a polymorphic class
 type [[class.virtual]], the result refers to a `std::type_info` object
 representing the type of the most derived object [[intro.object]] (that
+is, the dynamic type) to which the glvalue refers.
 When `typeid` is applied to an expression other than a glvalue of a
 polymorphic class type, the result refers to a `std::type_info` object
 representing the static type of the expression. Lvalue-to-rvalue
 [[conv.lval]], array-to-pointer [[conv.array]], and function-to-pointer
 `std::type_info` object representing the type of the *type-id*. If the
 type of the *type-id* is a reference to a possibly cv-qualified type,
 the result of the `typeid` expression refers to a `std::type_info`
 object representing the cv-unqualified referenced type.
+[*Note 2*: The *type-id* cannot denote a function type with a
 *cv-qualifier-seq* or a *ref-qualifier* [[dcl.fct]]. — *end note*]
 If the type of the expression or *type-id* is a cv-qualified type, the
 result of the `typeid` expression refers to a `std::type_info` object
 representing the cv-unqualified type.
 The type `std::type_info` [[type.info]] is not predefined; if a standard
 library declaration [[typeinfo.syn]], [[std.modules]] of
 `std::type_info` does not precede [[basic.lookup.general]] a `typeid`
 expression, the program is ill-formed.
+[*Note 3*: Subclause [[class.cdtor]] describes the behavior of `typeid`
 applied to an object under construction or destruction. — *end note*]
 #### Static cast <a id="expr.static.cast">[[expr.static.cast]]</a>
 The result of the expression `static_cast<T>(v)` is the result of
 converting the expression `v` to type `T`. If `T` is an lvalue reference
 type or an rvalue reference to function type, the result is an lvalue;
 if `T` is an rvalue reference to object type, the result is an xvalue;
+otherwise, the result is a prvalue.
 An lvalue of type “*cv1* `B`”, where `B` is a class type, can be cast to
+type “reference to *cv2* `D`”, where `D` is a complete class derived
 [[class.derived]] from `B`, if *cv2* is the same cv-qualification as, or
 greater cv-qualification than, *cv1*. If `B` is a virtual base class of
 `D` or a base class of a virtual base class of `D`, or if no valid
 standard conversion from “pointer to `D`” to “pointer to `B`” exists
 [[conv.ptr]], the program is ill-formed. An xvalue of type “*cv1* `B`”
 used as the operand of the `static_cast` for the remainder of this
 subclause. If `T2` is an inaccessible [[class.access]] or ambiguous
 [[class.member.lookup]] base class of `T1`, a program that necessitates
 such a cast is ill-formed.
+Any expression can be explicitly converted to type cv `void`, in which
+case the operand is a discarded-value expression [[expr.prop]].
+[*Note 1*: Such a `static_cast` has no result as it is a prvalue of
+type `void`; see  [[basic.lval]]. — *end note*]
+[*Note 2*: However, if the value is in a temporary object
+[[class.temporary]], the destructor for that object is not executed
+until the usual time, and the value of the object is preserved for the
+purpose of executing the destructor. — *end note*]
+Otherwise, an expression E can be explicitly converted to a type `T` if
+there is an implicit conversion sequence [[over.best.ics]] from E to
+`T`, if overload resolution for a direct-initialization [[dcl.init]] of
+an object or reference of type `T` from E would find at least one viable
 function [[over.match.viable]], or if `T` is an aggregate type
 [[dcl.init.aggr]] having a first element `x` and there is an implicit
 conversion sequence from E to the type of `x`. If `T` is a reference
 type, the effect is the same as performing the declaration and
 initialization
 for some invented temporary variable `t` [[dcl.init]] and then using the
 temporary variable as the result of the conversion. Otherwise, the
 result object is direct-initialized from E.
+[*Note 3*: The conversion is ill-formed when attempting to convert an
 expression of class type to an inaccessible or ambiguous base
 class. — *end note*]
+[*Note 4*: If `T` is “array of unknown bound of `U`”, this
 direct-initialization defines the type of the expression as
 `U[1]`. — *end note*]
+Otherwise, the lvalue-to-rvalue [[conv.lval]], array-to-pointer
+[[conv.array]], and function-to-pointer [[conv.func]] conversions are
+applied to the operand, and the conversions that can be performed using
+`static_cast` are listed below. No other conversion can be performed
+using `static_cast`.
 A value of a scoped enumeration type [[dcl.enum]] can be explicitly
 converted to an integral type; the result is the same as that of
 converting to the enumeration’s underlying type and then to the
 destination type. A value of a scoped enumeration type can also be
 If no valid standard conversion from “pointer to member of `B` of type
 `T`” to “pointer to member of `D` of type `T`” exists [[conv.mem]], the
 program is ill-formed. The null member pointer value [[conv.mem]] is
 converted to the null member pointer value of the destination type. If
+class `B` contains the original member, or is a base class of the class
+containing the original member, the resulting pointer to member points
+to the original member. Otherwise, the behavior is undefined.
 [*Note 6*: Although class `B` need not contain the original member, the
 dynamic type of the object with which indirection through the pointer to
 member is performed must contain the original member; see
 [[expr.mptr.oper]]. — *end note*]
 A prvalue of type “pointer to *cv1* `void`” can be converted to a
 prvalue of type “pointer to *cv2* `T`”, where `T` is an object type and
 *cv2* is the same cv-qualification as, or greater cv-qualification than,
 *cv1*. If the original pointer value represents the address `A` of a
 byte in memory and `A` does not satisfy the alignment requirement of
+`T`, then the resulting pointer value [[basic.compound]] is unspecified.
+Otherwise, if the original pointer value points to an object *a*, and
+there is an object *b* of type similar to `T` that is
+pointer-interconvertible [[basic.compound]] with *a*, the result is a
+pointer to *b*. Otherwise, the pointer value is unchanged by the
+conversion.
+[*Example 2*:
 ``` cpp
 T* p1 = new T;
 const T* p2 = static_cast<const T*>(static_cast<void*>(p1));
 bool b = p1 == p2;  // b will have the value true.
 any type to the type `std::nullptr_t`. — *end note*]
 A value of integral type or enumeration type can be explicitly converted
 to a pointer. A pointer converted to an integer of sufficient size (if
 any such exists on the implementation) and back to the same pointer type
+will have its original value [[basic.compound]]; mappings between
+pointers and integers are otherwise *implementation-defined*.
 A function pointer can be explicitly converted to a function pointer of
 a different type.
 [*Note 4*: The effect of calling a function through a pointer to a
 Except that converting a prvalue of type “pointer to `T1`” to the type
 “pointer to `T2`” (where `T1` and `T2` are function types) and back to
 its original type yields the original pointer value, the result of such
 a pointer conversion is unspecified.
 An object pointer can be explicitly converted to an object pointer of a
+different type.[^15]
 When a prvalue `v` of object pointer type is converted to the object
 pointer type “pointer to cv `T`”, the result is
 `static_cast<cv T*>(static_cast<cv~void*>(v))`.
+[*Note 5*: Converting a pointer of type “pointer to `T1`” that points
 to an object of type `T1` to the type “pointer to `T2`” (where `T2` is
 an object type and the alignment requirements of `T2` are no stricter
 than those of `T1`) and back to its original type yields the original
 pointer value. — *end note*]
 yield the original pointer value.
 The null pointer value [[basic.compound]] is converted to the null
 pointer value of the destination type.
+[*Note 6*: A null pointer constant of type `std::nullptr_t` cannot be
 converted to a pointer type, and a null pointer constant of integral
 type is not necessarily converted to a null pointer
 value. — *end note*]
 A prvalue of type “pointer to member of `X` of type `T1`” can be
 explicitly converted to a prvalue of a different type “pointer to member
 of `Y` of type `T2`” if `T1` and `T2` are both function types or both
+object types.[^16]
 The null member pointer value [[conv.mem]] is converted to the null
 member pointer value of the destination type. The result of this
 conversion is unspecified, except in the following cases:
   `T1`” to the type “pointer to data member of `Y` of type `T2`” (where
   the alignment requirements of `T2` are no stricter than those of `T1`)
   and back to its original type yields the original pointer-to-member
   value.
+If `v` is a glvalue of type `T1`, designating an object or function *x*,
+it can be cast to the type “reference to `T2`” if an expression of type
+“pointer to `T1`” can be explicitly converted to the type “pointer to
+`T2`” using a `reinterpret_cast`. The result is that of
+`*reinterpret_cast<T2 *>(p)` where `p` is a pointer to *x* of type
+“pointer to `T1`”.
+[*Note 7*:
+No temporary is materialized [[conv.rval]] or created, no copy is made,
+and no constructors [[class.ctor]] or conversion functions
+[[class.conv]] are called.[^17]
+— *end note*]
 #### Const cast <a id="expr.const.cast">[[expr.const.cast]]</a>
 The result of the expression `const_cast<T>(v)` is of type `T`. If `T`
 is an lvalue reference to object type, the result is an lvalue; if `T`
 is an rvalue reference to object type, the result is an xvalue;
 otherwise, the result is a prvalue and the lvalue-to-rvalue
 [[conv.lval]], array-to-pointer [[conv.array]], and function-to-pointer
 [[conv.func]] standard conversions are performed on the expression `v`.
+The temporary materialization conversion [[conv.rval]] is not performed
+on `v`, other than as specified below. Conversions that can be performed
+explicitly using `const_cast` are listed below. No other conversion
+shall be performed explicitly using `const_cast`.
 [*Note 1*: Subject to the restrictions in this subclause, an expression
 can be cast to its own type using a `const_cast`
 operator. — *end note*]
+For two similar object pointer or pointer to data member types `T1` and
+`T2` [[conv.qual]], a prvalue of type `T1` can be explicitly converted
+to the type `T2` using a `const_cast` if, considering the
+qualification-decompositions of both types, each P¹ᵢ is the same as P²ᵢ
+for all i. If `v` is a null pointer or null member pointer, the result
+is a null pointer or null member pointer, respectively. Otherwise, the
+result points to or past the end of the same object, or points to the
+same member, respectively, as `v`.
 For two object types `T1` and `T2`, if a pointer to `T1` can be
 explicitly converted to the type “pointer to `T2`” using a `const_cast`,
 then the following conversions can also be made:
 - an lvalue of type `T1` can be explicitly converted to an lvalue of
   type `T2` using the cast `const_cast<T2&>`;
 - a glvalue of type `T1` can be explicitly converted to an xvalue of
   type `T2` using the cast `const_cast<T2&&>`; and
+- if `T1` is a class or array type, a prvalue of type `T1` can be
+ explicitly converted to an xvalue of type `T2` using the cast
+  `const_cast<T2&&>`. The temporary materialization conversion is
+  performed on `v`.
+The result refers to the same object as the (possibly converted)
+operand.
+[*Example 1*:
+``` cpp
+typedef int *A[3];                  // array of 3 pointer to int
+typedef const int *const CA[3];     // array of 3 const pointer to const int
+auto &&r2 = const_cast<A&&>(CA{});  // OK, temporary materialization conversion is performed
+```
+— *end example*]
 [*Note 2*:
 Depending on the type of the object, a write operation through the
 pointer, lvalue or pointer to data member resulting from a `const_cast`
+that casts away a const-qualifier[^18]
 can produce undefined behavior [[dcl.type.cv]].
 — *end note*]
     sizeof '...' '(' identifier ')'
     alignof '(' type-id ')'
     noexcept-expression
     new-expression
     delete-expression
+    reflect-expression
 ```
 ``` bnf
 %% Ed. note: character protrusion would misalign operators.
 #### Unary operators <a id="expr.unary.op">[[expr.unary.op]]</a>
 The unary `*` operator performs *indirection*. Its operand shall be a
 prvalue of type “pointer to `T`”, where `T` is an object or function
+type. The operator yields an lvalue of type `T`. If the operand points
+to an object or function, the result denotes that object or function;
+otherwise, the behavior is undefined except as specified in
+[[expr.typeid]].
+[*Note 1*: Indirection through a pointer to an out-of-lifetime object
+is valid [[basic.life]]. — *end note*]
+[*Note 2*:  Indirection through a pointer to an incomplete type (other
 than cv `void`) is valid. The lvalue thus obtained can be used in
 limited ways (to initialize a reference, for example); this lvalue must
 not be converted to a prvalue, see  [[conv.lval]]. — *end note*]
 Each of the following unary operators yields a prvalue.
 The operand of the unary `&` operator shall be an lvalue of some type
+`T`.
+- If the operand is a *qualified-id* or *splice-expression* designating
+ a non-static member `m`, other than an explicit object member
+  function, `m` shall be a direct member of some class `C` that is not
+ an anonymous union. The result has type “pointer to member of class
+  `C` of type `T`” and designates `C::m`. \[*Note 3*: A *qualified-id*
+  that names a member of a namespace-scope anonymous union is considered
+  to be a class member access expression [[expr.prim.id.general]] and
+  cannot be used to form a pointer to member. — *end note*]
 - Otherwise, the result has type “pointer to `T`” and points to the
   designated object [[intro.memory]] or function [[basic.compound]]. If
+  the operand designates an explicit object member function [[dcl.fct]],
+ the operand shall be a *qualified-id* or a *splice-expression*.
+ \[*Note 4*: In particular, taking the address of a variable of type
+  “cv `T`” yields a pointer of type “pointer to cv `T`”. — *end note*]
 [*Example 1*:
 ``` cpp
 struct A { int i; };
 bool b = p2 > p1;   // defined behavior, with value true
 ```
 — *end example*]
+[*Note 5*: A pointer to member formed from a `mutable` non-static data
 member [[dcl.stc]] does not reflect the `mutable` specifier associated
 with the non-static data member. — *end note*]
 A pointer to member is only formed when an explicit `&` is used and its
+operand is a *qualified-id* or *splice-expression* not enclosed in
+parentheses.
+[*Note 6*: That is, the expression `&(qualified-id)`, where the
 *qualified-id* is enclosed in parentheses, does not form an expression
 of type “pointer to member”. Neither does `qualified-id`, because there
 is no implicit conversion from a *qualified-id* for a non-static member
 function to the type “pointer to member function” as there is from an
 lvalue of function type to the type “pointer to function” [[conv.func]].
 If `&` is applied to an lvalue of incomplete class type and the complete
 type declares `operator&()`, it is unspecified whether the operator has
 the built-in meaning or the operator function is called. The operand of
 `&` shall not be a bit-field.
+[*Note 7*: The address of an overload set [[over]] can be taken only in
 a context that uniquely determines which function is referred to (see
 [[over.over]]). Since the context can affect whether the operand is a
 static or non-static member function, the context can also affect
 whether the expression has type “pointer to function” or “pointer to
 member function”. — *end note*]
+The operand of the unary `+` operator shall be a prvalue of arithmetic,
+unscoped enumeration, or pointer type and the result is the value of the
 argument. Integral promotion is performed on integral or enumeration
 operands. The type of the result is the type of the promoted operand.
+The operand of the unary `-` operator shall be a prvalue of arithmetic
+or unscoped enumeration type and the result is the negative of its
+operand. Integral promotion is performed on integral or enumeration
+operands. The negative of an unsigned quantity is computed by
+subtracting its value from 2ⁿ, where n is the number of bits in the
+promoted operand. The type of the result is the type of the promoted
+operand.
+[*Note 8*: The result is the two’s complement of the operand (where
 operand and result are considered as unsigned). — *end note*]
 The operand of the logical negation operator `!` is contextually
 converted to `bool` [[conv]]; its value is `true` if the converted
 operand is `false` and `false` otherwise. The type of the result is
 `bool`.
+The operand of the `~` operator shall be a prvalue of integral or
+unscoped enumeration type. Integral promotions are performed. The type
+of the result is the type of the promoted operand. Given the
+coefficients `xᵢ` of the base-2 representation [[basic.fundamental]] of
+the promoted operand `x`, the coefficient `rᵢ` of the base-2
+representation of the result `r` is 1 if `xᵢ` is 0, and 0 otherwise.
+[*Note 9*: The result is the ones’ complement of the operand (where
 operand and result are considered as unsigned). — *end note*]
 There is an ambiguity in the grammar when `~` is followed by a
+*type-name* or *computed-type-specifier*. The ambiguity is resolved by
 treating `~` as the operator rather than as the start of an
 *unqualified-id* naming a destructor.
+[*Note 10*: Because the grammar does not permit an operator to follow
 the `.`, `->`, or `::` tokens, a `~` followed by a *type-name* or
+*computed-type-specifier* in a member access expression or
+*qualified-id* is unambiguously parsed as a destructor
+name. — *end note*]
 #### Increment and decrement <a id="expr.pre.incr">[[expr.pre.incr]]</a>
+The operand of prefix `++` or `--` shall not be of type cv `bool`. An
+operand with volatile-qualified type is deprecated; see
+[[depr.volatile.type]]. The expression `++x` is otherwise equivalent to
+`x+=1` and the expression `--x` is otherwise equivalent to `x-=1`
+[[expr.assign]].
+[*Note 1*: For postfix increment and decrement, see
 [[expr.post.incr]]. — *end note*]
 #### Await <a id="expr.await">[[expr.await]]</a>
 The `co_await` expression is used to suspend evaluation of a coroutine
 [[dcl.fct.def.coroutine]] while awaiting completion of the computation
+represented by the operand expression. Suspending the evaluation of a
+coroutine transfers control to its caller or resumer.
 ``` bnf
 await-expression:
+    co_await cast-expression
 ```
+An *await-expression* shall appear only as a potentially-evaluated
+expression within the *compound-statement* of a *function-body* or
+*lambda-expression*, in either case outside of a *handler*
+[[except.pre]]. In a *declaration-statement* or in the
 *simple-declaration* (if any) of an *init-statement*, an
 *await-expression* shall appear only in an *initializer* of that
 *declaration-statement* or *simple-declaration*. An *await-expression*
 shall not appear in a default argument [[dcl.fct.default]]. An
 *await-expression* shall not appear in the initializer of a block
+variable with static or thread storage duration. An *await-expression*
+shall not be a potentially-evaluated subexpression of the predicate of a
+contract assertion [[basic.contract]]. A context within a function where
+an *await-expression* can appear is called a *suspension context* of the
+function.
 Evaluation of an *await-expression* involves the following auxiliary
 types, expressions, and objects:
 - *p* is an lvalue naming the promise object [[dcl.fct.def.coroutine]]
 [*Note 1*:
 In particular, the values of `sizeof(bool)`, `sizeof(char16_t)`,
 `sizeof(char32_t)`, and `sizeof(wchar_t)` are
+implementation-defined.[^19]
 — *end note*]
 [*Note 2*: See  [[intro.memory]] for the definition of byte and
 [[term.object.representation]] for the definition of object
 When applied to a reference type, the result is the size of the
 referenced type. When applied to a class, the result is the number of
 bytes in an object of that class including any padding required for
 placing objects of that type in an array. The result of applying
 `sizeof` to a potentially-overlapping subobject is the size of the type,
+not the size of the subobject.[^20]
 When applied to an array, the result is the total number of bytes in the
 array. This implies that the size of an array of n elements is n times
 the size of an element.
 The lvalue-to-rvalue [[conv.lval]], array-to-pointer [[conv.array]], and
 function-to-pointer [[conv.func]] standard conversions are not applied
 to the operand of `sizeof`. If the operand is a prvalue, the temporary
 materialization conversion [[conv.rval]] is applied.
+The *identifier* in a `sizeof...` expression shall name a pack. The
 `sizeof...` operator yields the number of elements in the pack
 [[temp.variadic]]. A `sizeof...` expression is a pack expansion
 [[temp.variadic]].
 [*Example 1*:
 ``` cpp
 template<class... Types>
 struct count {
+  static constexpr std::size_t value = sizeof...(Types);
 };
 ```
 — *end example*]
 The result of `sizeof` and `sizeof...` is a prvalue of type
 `std::size_t`.
 [*Note 3*: A `sizeof` expression is an integral constant expression
+[[expr.const]]. The *typedef-name* `std::size_t` is declared in the
+standard header `<cstddef>`
+[[cstddef.syn]], [[support.types.layout]]. — *end note*]
 #### Alignof <a id="expr.alignof">[[expr.alignof]]</a>
 An `alignof` expression yields the alignment requirement of its operand
 type. The operand shall be a *type-id* representing a complete object
 type, or an array thereof, or a reference to one of those types.
 The result is a prvalue of type `std::size_t`.
 [*Note 1*: An `alignof` expression is an integral constant expression
+[[expr.const]]. The *typedef-name* `std::size_t` is declared in the
+standard header `<cstddef>`
+[[cstddef.syn]], [[support.types.layout]]. — *end note*]
 When `alignof` is applied to a reference type, the result is the
 alignment of the referenced type. When `alignof` is applied to an array
 type, the result is the alignment of the element type.
 #### `noexcept` operator <a id="expr.unary.noexcept">[[expr.unary.noexcept]]</a>
 ``` bnf
 noexcept-expression:
   noexcept '(' expression ')'
 ```
+The operand of the `noexcept` operator is an unevaluated operand
+[[term.unevaluated.operand]]. If the operand is a prvalue, the temporary
+materialization conversion [[conv.rval]] is applied.
+The result of the `noexcept` operator is a prvalue of type `bool`. The
+result is `false` if the full-expression of the operand is
+potentially-throwing [[except.spec]], and `true` otherwise.
 [*Note 1*: A *noexcept-expression* is an integral constant expression
 [[expr.const]]. — *end note*]
 #### New <a id="expr.new">[[expr.new]]</a>
+The *new-expression* attempts to create an object of the *type-id* or
+*new-type-id* [[dcl.name]] to which it is applied. The type of that
 object is the *allocated type*. This type shall be a complete object
 type [[term.incomplete.type]], but not an abstract class type
 [[class.abstract]] or array thereof [[intro.object]].
 [*Note 1*: Because references are not objects, references cannot be
 new-initializer:
     '(' expression-listₒₚₜ ')'
     braced-init-list
 ```
+If a placeholder type [[dcl.spec.auto]] or a placeholder for a deduced
+class type [[dcl.type.class.deduct]] appears in the *type-specifier-seq*
+of a *new-type-id* or *type-id* of a *new-expression*, the allocated
+type is deduced as follows: Let *init* be the *new-initializer*, if any,
+and `T` be the *new-type-id* or *type-id* of the *new-expression*, then
+the allocated type is the type deduced for the variable `x` in the
+invented declaration [[dcl.spec.auto]]:
 ``` cpp
 T x init ;
 ```
 its value shall be greater than zero.
 [*Example 4*: Given the definition `int n = 42`, `new float[n][5]` is
 well-formed (because `n` is the *expression* of a
 *noptr-new-declarator*), but `new float[5][n]` is ill-formed (because
+`n` is not a constant expression). Furthermore, `new float[0]` is
+well-formed (because `0` is the *expression* of a
+*noptr-new-declarator*, where a value of zero results in the allocation
+of an array with no elements), but `new float[n][0]` is ill-formed
+(because `0` is the *constant-expression* of a *noptr-new-declarator*,
+where only values greater than zero are allowed). — *end example*]
 If the *type-id* or *new-type-id* denotes an array type of unknown bound
 [[dcl.array]], the *new-initializer* shall not be omitted; the allocated
 object is an array with `n` elements, where `n` is determined from the
 number of initial elements supplied in the *new-initializer*
 [[dcl.init.aggr]], [[dcl.init.string]].
 If the *expression* in a *noptr-new-declarator* is present, it is
+implicitly converted to `std::size_t`. The value of the *expression* is
+invalid if
 - the expression is of non-class type and its value before converting to
   `std::size_t` is less than zero;
 - the expression is of class type and its value before application of
+  the second standard conversion [[over.ics.user]][^21] is less than
   zero;
 - its value is such that the size of the allocated object would exceed
   the *implementation-defined* limit [[implimits]]; or
 - the *new-initializer* is a *braced-init-list* and the number of array
   elements for which initializers are provided (including the
   terminating `'\0'` in a *string-literal* [[lex.string]]) exceeds the
   number of elements to initialize.
+If the value of the *expression* is invalid after converting to
+`std::size_t`:
 - if the *expression* is a potentially-evaluated core constant
   expression, the program is ill-formed;
 - otherwise, an allocation function is not called; instead
   - if the allocation function that would have been called has a
     `std::bad_array_new_length` [[new.badlength]].
 When the value of the *expression* is zero, the allocation function is
 called to allocate an array with no elements.
+If the allocated type is an array, the *new-initializer* is a
+*braced-init-list*, and the *expression* is potentially-evaluated and
+not a core constant expression, the semantic constraints of
+copy-initializing a hypothetical element of the array from an empty
+initializer list are checked [[dcl.init.list]].
+[*Note 5*: The array can contain more elements than there are elements
+in the *braced-init-list*, requiring initialization of the remainder of
+the array elements from an empty initializer list. — *end note*]
 Objects created by a *new-expression* have dynamic storage duration
 [[basic.stc.dynamic]].
+[*Note 6*:  The lifetime of such an object is not necessarily
 restricted to the scope in which it is created. — *end note*]
 When the allocated type is “array of `N` `T`” (that is, the
 *noptr-new-declarator* syntax is used or the *new-type-id* or *type-id*
 denotes an array type), the *new-expression* yields a prvalue of type
 “pointer to `T`” that points to the initial element (if any) of the
 array. Otherwise, let `T` be the allocated type; the *new-expression* is
 a prvalue of type “pointer to T” that points to the object created.
+[*Note 7*: Both `new int` and `new int[10]` have type `int*` and the
 type of `new int[i][10]` is `int (*)[10]`. — *end note*]
 A *new-expression* may obtain storage for the object by calling an
 allocation function [[basic.stc.dynamic.allocation]]. If the
 *new-expression* terminates by throwing an exception, it may release
 type, the allocation function’s name is `operator new` and the
 deallocation function’s name is `operator delete`. If the allocated type
 is an array type, the allocation function’s name is `operator new[]` and
 the deallocation function’s name is `operator delete[]`.
+[*Note 8*: An implementation is expected to provide default definitions
 for the global allocation functions
 [[basic.stc.dynamic]], [[new.delete.single]], [[new.delete.array]]. A
 C++ program can provide alternative definitions of these functions
 [[replacement.functions]] and/or class-specific versions [[class.free]].
 The set of allocation and deallocation functions that can be called by a
 An implementation is allowed to omit a call to a replaceable global
 allocation function [[new.delete.single]], [[new.delete.array]]. When it
 does so, the storage is instead provided by the implementation or
 provided by extending the allocation of another *new-expression*.
+During an evaluation of a constant expression, a call to a replaceable
+allocation function is always omitted [[expr.const]].
 The implementation may extend the allocation of a *new-expression* `e1`
 to provide storage for a *new-expression* `e2` if the following would be
 true were the allocation not extended:
 value of the *new-expression* shall be null.
 [*Note 11*: When the allocation function returns a value other than
 null, it must be a pointer to a block of storage in which space for the
 object has been reserved. The block of storage is assumed to be
+appropriately aligned [[basic.align]] and of the requested size. The
+address of the created object will not necessarily be the same as that
+of the block if the object is an array. — *end note*]
 A *new-expression* that creates an object of type `T` initializes that
 object as follows:
 - If the *new-initializer* is omitted, the object is default-initialized
 The invocation of the allocation function is sequenced before the
 evaluations of expressions in the *new-initializer*. Initialization of
 the allocated object is sequenced before the value computation of the
 *new-expression*.
+If the *new-expression* creates an array of objects of class type, the
+destructor is potentially invoked [[class.dtor]].
+If any part of the object initialization described above[^22]
 terminates by throwing an exception and a suitable deallocation function
 can be found, the deallocation function is called to free the memory in
 which the object was being constructed, after which the exception
 continues to propagate in the context of the *new-expression*. If no
 otherwise, no deallocation function will be called. If the lookup finds
 a usual deallocation function and that function, considered as a
 placement deallocation function, would have been selected as a match for
 the allocation function, the program is ill-formed. For a non-placement
 allocation function, the normal deallocation function lookup is used to
+find the matching deallocation function [[expr.delete]]. In any case,
+the matching deallocation function (if any) shall be non-deleted and
+accessible from the point where the *new-expression* appears.
 [*Example 7*:
 ``` cpp
 struct S {
 ```
 The first alternative is a *single-object delete expression*, and the
 second is an *array delete expression*. Whenever the `delete` keyword is
 immediately followed by empty square brackets, it shall be interpreted
+as the second alternative.[^23]
+If the operand is of class type, it is contextually implicitly converted
+[[conv]] to a pointer to object type and the converted operand is used
+in place of the original operand for the remainder of this subclause.
+Otherwise, it shall be a prvalue of pointer to object type. The
+*delete-expression* has type `void`.
+In a single-object delete expression, the value of the operand of
+`delete` may be a null pointer value, a pointer value that resulted from
+a previous non-array *new-expression*, or a pointer to a base class
+subobject of an object created by such a *new-expression*. If not, the
+behavior is undefined. In an array delete expression, the value of the
+operand of `delete` may be a null pointer value or a pointer value that
+resulted from a previous array *new-expression* whose allocation
+function was not a non-allocating form [[new.delete.placement]].[^24]
 If not, the behavior is undefined.
 [*Note 1*: This means that the syntax of the *delete-expression* must
 match the type of the object allocated by `new`, not the syntax of the
 object to be deleted and the static type shall have a virtual destructor
 or the behavior is undefined. In an array delete expression, if the
 dynamic type of the object to be deleted is not similar to its static
 type, the behavior is undefined.
 If the object being deleted has incomplete class type at the point of
+deletion, the program is ill-formed.
 If the value of the operand of the *delete-expression* is not a null
 pointer value and the selected deallocation function (see below) is not
+a destroying operator delete, evaluating the *delete-expression* invokes
+the destructor (if any) for the object or the elements of the array
+being deleted. The destructor shall be accessible from the point where
+the *delete-expression* appears. In the case of an array, the elements
+are destroyed in order of decreasing address (that is, in reverse order
+of the completion of their constructor; see  [[class.base.init]]).
 If the value of the operand of the *delete-expression* is not a null
 pointer value, then:
 - If the allocation call for the *new-expression* for the object to be
 [*Note 5*: If only a placement deallocation function is found in a
 class, the program is ill-formed because the lookup set is empty
 [[basic.lookup]]. — *end note*]
+The deallocation function to be called is selected as follows:
 - If any of the deallocation functions is a destroying operator delete,
   all deallocation functions that are not destroying operator deletes
   are eliminated from further consideration.
 - If the type has new-extended alignment, a function with a parameter of
   or a (possibly multidimensional) array thereof, the function with a
   parameter of type `std::size_t` is selected.
 - Otherwise, it is unspecified whether a deallocation function with a
   parameter of type `std::size_t` is selected.
+Unless the deallocation function is selected at the point of definition
+of the dynamic type’s virtual destructor, the selected deallocation
+function shall be accessible from the point where the
+*delete-expression* appears.
 For a single-object delete expression, the deleted object is the object
 A pointed to by the operand if the static type of A does not have a
 virtual destructor, and the most-derived object of A otherwise.
 [*Note 6*: If the deallocation function is not a destroying operator
 function, and either the first argument was not the result of a prior
 call to a replaceable allocation function or the second or third
 argument was not the corresponding argument in said call, the behavior
 is undefined [[new.delete.single]], [[new.delete.array]]. — *end note*]
+#### The reflection operator <a id="expr.reflect">[[expr.reflect]]</a>
+``` bnf
+reflect-expression:
+    '^^' '::'
+    '^^' reflection-name
+    '^^' type-id
+    '^^' id-expression
+```
+``` bnf
+reflection-name:
+    nested-name-specifierₒₚₜ identifier
+    nested-name-specifier template identifier
+```
+The unary `^^` operator, called the *reflection operator*, yields a
+prvalue of type `std::meta::info` [[basic.fundamental]].
+[*Note 1*: This document places no restriction on representing, by
+reflections, constructs not described by this document or using the
+names of such constructs as operands of
+*reflect-expression*s. — *end note*]
+The component names of a *reflection-name* are those of its
+*nested-name-specifier* (if any) and its *identifier*. The terminal name
+of a *reflection-name* of the form *nested-name-specifier* `template`
+*identifier* shall denote a template.
+A *reflect-expression* is parsed as the longest possible sequence of
+tokens that could syntactically form a *reflect-expression*. An
+unparenthesized *reflect-expression* that represents a template shall
+not be followed by `<`.
+[*Example 1*:
+``` cpp
+static_assert(std::meta::is_type(^^int()));     // ^^ applies to the type-id int()
+template<bool> struct X {};
+consteval bool operator<(std::meta::info, X<false>) { return false; }
+consteval void g(std::meta::info r, X<false> xv) {
+  r == ^^int && true;       // error: ^^ applies to the type-id int&&
+  r == ^^int & true;        // error: ^^ applies to the type-id int&
+  r == (^^int) && true;     // OK
+  r == ^^int &&&& true;     // error: int &&&& is not a valid type-id
+  ^^X < xv;                 // error: reflect-expression that represents a template is followed by <
+  (^^X) < xv;               // OK
+  ^^X<true> < xv;           // OK
+}
+```
+— *end example*]
+A *reflect-expression* of the form `^^ ::` represents the global
+namespace.
+If a *reflect-expression* R matches the form `^^ reflection-name`, it is
+interpreted as such; the *identifier* is looked up and the
+representation of R is determined as follows:
+- If lookup finds a declaration that replaced a *using-declarator*
+  during a single search [[basic.lookup.general]], [[namespace.udecl]],
+  R is ill-formed.
+  \[*Example 2*:
+  ``` cpp
+  struct A { struct S {}; };
+  struct B : A { using A::S; };
+  constexpr std::meta::info r1 = ^^B::S;  // error: A::S found through using-declarator
+  struct C : virtual B { struct S {}; };
+  struct D : virtual B, C {};
+  D::S s;                                 // OK, names C::S per [class.member.lookup]
+  constexpr std::meta::info r2 = ^^D::S;  // OK, result C::S not found through using-declarator
+  ```
+  — *end example*]
+- Otherwise, if lookup finds a namespace alias [[namespace.alias]], R
+  represents that namespace alias.
+- Otherwise, if lookup finds a namespace [[basic.namespace]], R
+  represents that namespace.
+- Otherwise, if lookup finds a concept [[temp.concept]], R represents
+  the denoted concept.
+- Otherwise, if lookup finds a template [[temp.names]], the
+  representation of R is determined as follows:
+  - If lookup finds an injected-class-name [[class.pre]], then:
+    - If the *reflection-name* is of the form
+      `nested-name-specifier template identifier`, then R represents the
+      class template named by the injected-class-name.
+    - Otherwise, the injected-class-name shall be unambiguous when
+      considered as a *type-name* and R represents the class template
+      specialization so named.
+  - Otherwise, if lookup finds an overload set, that overload set shall
+    contain only declarations of a unique function template F; R
+    represents F.
+  - Otherwise, if lookup finds a class template, variable template, or
+    alias template, R represents that template. \[*Note 2*: Lookup never
+    finds a partial or explicit specialization. — *end note*]
+- Otherwise, if lookup finds a type alias A, R represents the underlying
+  entity of A if A was introduced by the declaration of a template
+  parameter; otherwise, R represents A.
+- Otherwise, if lookup finds a class or an enumeration, R represents the
+  denoted type.
+- Otherwise, if lookup finds a class member of an anonymous union
+  [[class.union.anon]], R represents that class member.
+- Otherwise, the *reflection-name* shall be an *id-expression* `I` and R
+  is `^^ I` (see below).
+A *reflect-expression* R of the form `^^ type-id` represents an entity
+determined as follows:
+- If the *type-id* designates a placeholder type
+  [[dcl.spec.auto.general]], R is ill-formed.
+- Otherwise, if the *type-id* names a type alias that is a
+  specialization of an alias template [[temp.alias]], R represents that
+  type alias.
+- Otherwise, R represents the type denoted by the *type-id*.
+A *reflect-expression* R of the form `^^ id-expression` represents an
+entity determined as follows:
+- If the *id-expression* denotes
+  - a variable declared by an *init-capture*
+    [[expr.prim.lambda.capture]],
+  - a function-local predefined variable [[dcl.fct.def.general]],
+  - a local parameter introduced by a *requires-expression*
+    [[expr.prim.req]], or
+  - a local entity E [[basic.pre]] for which a lambda scope intervenes
+    between the point at which E was introduced and R,
+  then R is ill-formed.
+- Otherwise, if the *id-expression* denotes an overload set S, overload
+  resolution for the expression `&S` with no target shall select a
+  unique function [[over.over]]; R represents that function.
+- Otherwise, if the *id-expression* denotes a variable, structured
+  binding, enumerator, or non-static data member, R represents that
+  entity.
+- Otherwise, R is ill-formed. \[*Note 3*: This includes
+  *unqualified-id*s that name a constant template parameter and
+  *pack-index-expression*s. — *end note*]
+The *id-expression* of a *reflect-expression* is an unevaluated operand
+[[expr.context]].
+[*Example 3*:
+``` cpp
+template<typename T> void fn() requires (^^T != ^^int);
+template<typename T> void fn() requires (^^T == ^^int);
+template<typename T> void fn() requires (sizeof(T) == sizeof(int));
+constexpr std::meta::info a = ^^fn<char>;       // OK
+constexpr std::meta::info b = ^^fn<int>;        // error: ambiguous
+constexpr std::meta::info c = ^^std::vector;    // OK
+template<typename T>
+struct S {
+  static constexpr std::meta::info r = ^^T;
+  using type = T;
+};
+static_assert(S<int>::r == ^^int);
+static_assert(^^S<int>::type != ^^int);
+typedef struct X {} Y;
+typedef struct Z {} Z;
+constexpr std::meta::info e = ^^Y;              // OK, represents the type alias Y
+constexpr std::meta::info f = ^^Z;              // OK, represents the type alias Z, not the type[basic.lookup.general]
+```
+— *end example*]
 ### Explicit type conversion (cast notation) <a id="expr.cast">[[expr.cast]]</a>
 The result of the expression `(T)` *cast-expression* is of type `T`. The
 result is an lvalue if `T` is an lvalue reference type or an rvalue
   of a derived class type, respectively.
 If a conversion can be interpreted in more than one of the ways listed
 above, the interpretation that appears first in the list is used, even
 if a cast resulting from that interpretation is ill-formed. If a
+`static_cast` followed by a `const_cast` is used and the conversion can
+be interpreted in more than one way as such, the conversion is
+ill-formed.
 [*Example 1*:
 ``` cpp
 struct A { };
 struct I2 : A { };
 struct D : I1, I2 { };
 A* foo( D* p ) {
   return (A*)( p );             // ill-formed static_cast interpretation
 }
+int*** ptr = 0;
+auto t = (int const*const*const*)ptr;   // OK, const_cast interpretation
+struct S {
+  operator const int*();
+  operator volatile int*();
+};
+int *p = (int*)S();     // error: two possible interpretations using static_cast followed by const_cast
 ```
 — *end example*]
 The operand of a cast using the cast notation can be a prvalue of type
 incomplete, it is unspecified whether the `static_cast` or the
 `reinterpret_cast` interpretation is used, even if there is an
 inheritance relationship between the two classes.
 [*Note 2*: For example, if the classes were defined later in the
+translation unit, a multi-pass compiler could validly interpret a cast
+between pointers to the classes as if the class types were complete at
+the point of the cast. — *end note*]
 ### Pointer-to-member operators <a id="expr.mptr.oper">[[expr.mptr.oper]]</a>
 The pointer-to-member operators `->*` and `.*` group left-to-right.
     cast-expression
     pm-expression '.*' cast-expression
     pm-expression '->*' cast-expression
 ```
+The binary operator `.*` binds its second operand, which shall be a
+prvalue of type “pointer to member of `T`” to its first operand, which
+shall be a glvalue of class `T` or of a class of which `T` is an
+unambiguous and accessible base class. The result is an object or a
+function of the type specified by the second operand.
+The binary operator `->*` binds its second operand, which shall be a
+prvalue of type “pointer to member of `T`” to its first operand, which
+shall be of type “pointer to `U`” where `U` is either `T` or a class of
+which `T` is an unambiguous and accessible base class. The expression
+`E1->*E2` is converted into the equivalent form `(*(E1)).*E2`.
 Abbreviating *pm-expression*`.*`*cast-expression* as `E1.*E2`, `E1` is
 called the *object expression*. If the result of `E1` is an object whose
 type is not similar to the type of `E1`, or whose most derived object
 does not contain the member to which `E2` refers, the behavior is
 The binary `*` operator indicates multiplication.
 The binary `/` operator yields the quotient, and the binary `%` operator
 yields the remainder from the division of the first expression by the
+second. If the second operand of `/` or `%` is zero, the behavior is
+undefined. For integral operands, the `/` operator yields the algebraic
+quotient with any fractional part discarded;[^25]
 if the quotient `a/b` is representable in the type of the result,
 `(a/b)*b + a%b` is equal to `a`; otherwise, the behavior of both `a/b`
 and `a%b` is undefined.
 ### Additive operators <a id="expr.add">[[expr.add]]</a>
+The additive operators `+` and `-` group left-to-right. Each operand
+shall be a prvalue. If both operands have arithmetic or unscoped
+enumeration type, the usual arithmetic conversions [[expr.arith.conv]]
+are performed. Otherwise, if one operand has arithmetic or unscoped
+enumeration type, integral promotion is applied [[conv.prom]] to that
+operand. A converted or promoted operand is used in place of the
+corresponding original operand for the remainder of this section.
 ``` bnf
 additive-expression:
     multiplicative-expression
     additive-expression '+' multiplicative-expression
     additive-expression '-' multiplicative-expression
 ```
+For addition, either both operands shall have arithmetic type, or one
+operand shall be a pointer to a completely-defined object type and the
+other shall have integral type.
 For subtraction, one of the following shall hold:
+- both operands have arithmetic type; or
 - both operands are pointers to cv-qualified or cv-unqualified versions
   of the same completely-defined object type; or
 - the left operand is a pointer to a completely-defined object type and
+  the right operand has integral type.
 The result of the binary `+` operator is the sum of the operands. The
 result of the binary `-` operator is the difference resulting from the
 subtraction of the second operand from the first.
 When an expression `J` that has integral type is added to or subtracted
 from an expression `P` of pointer type, the result has the type of `P`.
 - If `P` evaluates to a null pointer value and `J` evaluates to 0, the
   result is a null pointer value.
+- Otherwise, if `P` points to a (possibly-hypothetical) array element i
+ of an array object `x` with n elements [[dcl.array]],[^26] the
+ expressions `P + J` and `J + P` (where `J` has the value j) point to
+ the (possibly-hypothetical) array element i + j of `x` if
+ 0 ≤ i + j ≤ n and the expression `P - J` points to the
+ (possibly-hypothetical) array element i - j of `x` if 0 ≤ i - j ≤ n.
 - Otherwise, the behavior is undefined.
 [*Note 1*: Adding a value other than 0 or 1 to a pointer to a base
 class subobject, a member subobject, or a complete object results in
 undefined behavior. — *end note*]
 When two pointer expressions `P` and `Q` are subtracted, the type of the
 result is an *implementation-defined* signed integral type; this type
+shall be the same type that is named by `std::ptrdiff_t` in the
 `<cstddef>` header [[support.types.layout]].
 - If `P` and `Q` both evaluate to null pointer values, the result is 0.
 - Otherwise, if `P` and `Q` point to, respectively, array elements i and
   j of the same array object `x`, the expression `P - Q` has the value
+  i - j. \[*Note 2*: If the value i - j is not in the range of
+  representable values of type `std::ptrdiff_t`, the behavior is
+ undefined [[expr.pre]]. — *end note*]
+- Otherwise, the behavior is undefined.
 For addition or subtraction, if the expressions `P` or `Q` have type
 “pointer to cv `T`”, where `T` and the array element type are not
 similar [[conv.qual]], the behavior is undefined.
     additive-expression
     shift-expression '<<' additive-expression
     shift-expression '>>' additive-expression
 ```
+The operands shall be prvalues of integral or unscoped enumeration type
+and integral promotions are performed. The type of the result is that of
+the promoted left operand. The behavior is undefined if the right
+operand is negative, or greater than or equal to the width of the
+promoted left operand.
 The value of `E1 << E2` is the unique value congruent to `E1` × 2^`E2`
 modulo 2ᴺ, where N is the width of the type of the result.
 [*Note 1*: `E1` is left-shifted `E2` bit positions; vacated bits are
 zero-filled. — *end note*]
+The value of `E1 >> E2` is `E1` / 2^`E2`, rounded towards negative
+infinity.
 [*Note 2*: `E1` is right-shifted `E2` bit positions. Right-shift on
 signed integral types is an arithmetic right shift, which performs
 sign-extension. — *end note*]
     relational-expression '>' compare-expression
     relational-expression '<=' compare-expression
     relational-expression '>=' compare-expression
 ```
+The lvalue-to-rvalue [[conv.lval]] and function-to-pointer [[conv.func]]
+standard conversions are performed on the operands. If one of the
+operands is a pointer, the array-to-pointer conversion [[conv.array]] is
+performed on the other operand.
 The converted operands shall have arithmetic, enumeration, or pointer
 type. The operators `<` (less than), `>` (greater than), `<=` (less than
 or equal to), and `>=` (greater than or equal to) all yield `false` or
 `true`. The type of the result is `bool`.
 The usual arithmetic conversions [[expr.arith.conv]] are performed on
+operands of arithmetic or enumeration type. If both converted operands
+are pointers, pointer conversions [[conv.ptr]], function pointer
+conversions [[conv.fctptr]], and qualification conversions [[conv.qual]]
+are performed to bring them to their composite pointer type
+[[expr.type]]. After conversions, the operands shall have the same type.
+The result of comparing unequal pointers to objects[^27]
 is defined in terms of a partial order consistent with the following
 rules:
 - If two pointers point to different elements of the same array, or to
 `p>q`, `q<=p`, and `q<p` all yield `true` and `p<=q`, `p<q`, `q>=p`, and
 `q>p` all yield `false`. Otherwise, the result of each of the operators
 is unspecified.
 [*Note 1*: A relational operator applied to unequal function pointers
+yields an unspecified result. A pointer value of type “pointer to
+cv `void`” can point to an object [[basic.compound]]. — *end note*]
 If both operands (after conversions) are of arithmetic or enumeration
 type, each of the operators shall yield `true` if the specified
 relationship is true and `false` if it is false.
     equality-expression '==' relational-expression
     equality-expression '!=' relational-expression
 ```
 The `==` (equal to) and the `!=` (not equal to) operators group
+left-to-right. The lvalue-to-rvalue [[conv.lval]] and
+function-to-pointer [[conv.func]] standard conversions are performed on
+the operands. If one of the operands is a pointer or a null pointer
+constant [[conv.ptr]], the array-to-pointer conversion [[conv.array]] is
+performed on the other operand.
+The converted operands shall have scalar type. The operators `==` and
 `!=` both yield `true` or `false`, i.e., a result of type `bool`. In
 each case below, the operands shall have the same type after the
 specified conversions have been applied.
+If at least one of the converted operands is a pointer, pointer
+conversions [[conv.ptr]], function pointer conversions [[conv.fctptr]],
+and qualification conversions [[conv.qual]] are performed on both
+operands to bring them to their composite pointer type [[expr.type]].
+Comparing pointers is defined as follows:
 - If one pointer represents the address of a complete object, and
   another pointer represents the address one past the last element of a
+  different complete object,[^28] the result of the comparison is
   unspecified.
 - Otherwise, if the pointers are both null, both point to the same
   function, or both represent the same address [[basic.compound]], they
   compare equal.
 - Otherwise, the pointers compare unequal.
   — *end example*]
 Two operands of type `std::nullptr_t` or one operand of type
 `std::nullptr_t` and the other a null pointer constant compare equal.
+If both operands are of type `std::meta::info`, they compare equal if
+both operands
+- are null reflection values,
+- represent values that are template-argument-equivalent [[temp.type]],
+- represent the same object,
+- represent the same entity,
+- represent the same annotation [[dcl.attr.annotation]],
+- represent the same direct base class relationship, or
+- represent equal data member descriptions [[class.mem.general]],
+and they compare unequal otherwise.
 If two operands compare equal, the result is `true` for the `==`
 operator and `false` for the `!=` operator. If two operands compare
 unequal, the result is `false` for the `==` operator and `true` for the
 `!=` operator. Otherwise, the result of each of the operators is
 unspecified.
   but an implicit conversion sequence can only be formed if the
   reference would bind directly.
 - If `E2` is a prvalue or if neither of the conversion sequences above
   can be formed and at least one of the operands has (possibly
   cv-qualified) class type:
+  - if `T1` and `T2` are the same class type (ignoring
+    cv-qualification):
+    - if `T2` is at least as cv-qualified as `T1`, the target type is
       `T2`,
+    - otherwise, no conversion sequence is formed for this operand;
   - otherwise, if `T2` is a base class of `T1`, the target type is *cv1*
+    `T2`, where *cv1* denotes the cv-qualifiers of `T1`;
   - otherwise, the target type is the type that `E2` would have after
     applying the lvalue-to-rvalue [[conv.lval]], array-to-pointer
     [[conv.array]], and function-to-pointer [[conv.func]] standard
     conversions.
 Using this process, it is determined whether an implicit conversion
 sequence can be formed from the second operand to the target type
+determined for the third operand, and vice versa, with the following
+outcome:
+- If both sequences can be formed, or one can be formed but it is the
+  ambiguous conversion sequence, the program is ill-formed.
+- If no conversion sequence can be formed, the operands are left
+  unchanged and further checking is performed as described below.
+- Otherwise, if exactly one conversion sequence can be formed, that
+  conversion is applied to the chosen operand and the converted operand
+  is used in place of the original operand for the remainder of this
+  subclause. \[*Note 3*: The conversion might be ill-formed even if an
+  implicit conversion sequence could be formed. — *end note*]
 If the second and third operands are glvalues of the same value category
 and have the same type, the result is of that type and value category
 and it is a bit-field if the second or the third operand is a bit-field,
 or if both are bit-fields.
 the overload resolution fails, the program is ill-formed. Otherwise, the
 conversions thus determined are applied, and the converted operands are
 used in place of the original operands for the remainder of this
 subclause.
+Array-to-pointer [[conv.array]] and function-to-pointer [[conv.func]]
+standard conversions are performed on the second and third operands.
+After those conversions, one of the following shall hold:
 - The second and third operands have the same type; the result is of
+  that type and the result is copy-initialized using the selected
   operand.
 - The second and third operands have arithmetic or enumeration type; the
   usual arithmetic conversions [[expr.arith.conv]] are performed to
   bring them to a common type, and the result is of that type.
 - One or both of the second and third operands have pointer type;
+ lvalue-to-rvalue [[conv.lval]], pointer [[conv.ptr]], function pointer
   [[conv.fctptr]], and qualification conversions [[conv.qual]] are
   performed to bring them to their composite pointer type [[expr.type]].
   The result is of the composite pointer type.
 - One or both of the second and third operands have pointer-to-member
+  type; lvalue-to-rvalue [[conv.lval]], pointer to member [[conv.mem]],
+ function pointer [[conv.fctptr]], and qualification conversions
   [[conv.qual]] are performed to bring them to their composite pointer
   type [[expr.type]]. The result is of the composite pointer type.
 - Both the second and third operands have type `std::nullptr_t` or one
   has that type and the other is a null pointer constant. The result is
   of type `std::nullptr_t`.
 ### Yielding a value <a id="expr.yield">[[expr.yield]]</a>
 ``` bnf
 yield-expression:
+  co_yield assignment-expression
+  co_yield braced-init-list
 ```
 A *yield-expression* shall appear only within a suspension context of a
 function [[expr.await]]. Let *e* be the operand of the
 *yield-expression* and *p* be an lvalue naming the promise object of the
     throw assignment-expressionₒₚₜ
 ```
 A *throw-expression* is of type `void`.
+A *throw-expression* with an operand throws an exception
+[[except.throw]]. The array-to-pointer [[conv.array]] and
+function-to-pointer [[conv.func]] standard conversions are performed on
+the operand. The type of the exception object is determined by removing
+any top-level *cv-qualifier*s from the type of the (possibly converted)
+operand. The exception object is copy-initialized [[dcl.init.general]]
+from the (possibly converted) operand.
 A *throw-expression* with no operand rethrows the currently handled
+exception [[except.handle]]. If no exception is presently being handled,
+the function `std::terminate` is invoked [[except.terminate]].
+Otherwise, the exception is reactivated with the existing exception
+object; no new exception object is created. The exception is no longer
+considered to be caught.
 [*Example 1*:
 An exception handler that cannot completely handle the exception itself
 can be written like this:
 }
 ```
 — *end example*]
+### Assignment and compound assignment operators <a id="expr.assign">[[expr.assign]]</a>
 The assignment operator (`=`) and the compound assignment operators all
 group right-to-left. All require a modifiable lvalue as their left
 operand; their result is an lvalue of the type of the left operand,
 referring to the left operand. The result in all cases is a bit-field if
 ``` bnf
 assignment-operator: one of
     '= *= /= %= += -= >>= <<= &= ^= |='
 ```
+In simple assignment (`=`), let `V` be the result of the right operand;
+the object referred to by the left operand is modified [[defns.access]]
+by replacing its value with `V` or, if the object is of integer type,
+with the value congruent [[basic.fundamental]] to `V`.
 If the right operand is an expression, it is implicitly converted
 [[conv]] to the cv-unqualified type of the left operand.
 When the left operand of an assignment operator is a bit-field that
 [*Note 3*: This restriction applies to the relationship between the
 left and right sides of the assignment operation; it is not a statement
 about how the target of the assignment can be aliased in general. See
 [[basic.lval]]. — *end note*]
+A *braced-init-list* B may appear on the right-hand side of
+- an assignment to a scalar of type `T`, in which case B shall have at
+  most a single element. The meaning of `x = B` is `x = t`, where `t` is
+ an invented temporary variable declared and initialized as `T t = B`.
+- an assignment to an object of class type, in which case B is passed as
+  the argument to the assignment operator function selected by overload
+ resolution [[over.assign]], [[over.match]].
 [*Example 1*:
 ``` cpp
 complex<double> z;

Diff to HTML by rtfpessoa