This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of WP status.

3200. midpoint should not constrain T is complete

Section: 25.10.15 [numeric.ops.midpoint] Status: WP Submitter: Paolo Torres Opened: 2019-04-10 Last modified: 2020-09-06

Priority: 2

View all issues with WP status.

Discussion:

The constraint of the midpoint overload in 25.10.15 [numeric.ops.midpoint]:

template<class T>
constexpr T* midpoint(T* a, T* b);

-4- Constraints: T is a complete object type.

is incorrect. Paragraph 4 states T is constrained to be a complete object type, however it does not seem to be possible to implement T is complete. This means behavior is conditioned dependent on whether a type is complete, and this seems inconsistent with the library precedent.

[2019-06-12 Priority set to 2 after reflector discussion]

[2020-02 Status to Immediate on Thursday night in Prague.]

Proposed resolution:

This wording is relative to N4810.

  1. Modify 25.10.15 [numeric.ops.midpoint] as indicated:

    template<class T>
      constexpr T* midpoint(T* a, T* b);
    

    -4- Constraints: T is an complete object type.

    -?- Mandates: T is a complete type.

    […]