std::pointer_traits should be SFINAE-friendly
Glen Joseph Fernandes

Created on 2021-04-20.00:00:00 last changed yesterday


Date: 2021-05-10.16:30:18

Proposed resolution:

This wording is relative to N4885.

  1. Modify [pointer.traits.types] as indicated:

    As additional drive-by fix the improper usage of the term "instantiation" has been corrected.

    using element_type = see below;

    -1- Type: Ptr::element_type if the qualified-id Ptr::element_type is valid and denotes a type ([temp.deduct]); otherwise, T if Ptr is a class template instantiationspecialization of the form SomePointer<T, Args>, where Args is zero or more type arguments; otherwise, the specialization is ill-formedpointer_traits has no member element_type.

Date: 2021-05-15.00:00:00

[ 2021-05-10; Reflector poll ]

Priority set to 2. Send to LEWG. Daniel: "there is no similar treatment for the rebind member template and I think it should be clarified whether pointer_to's signature should exist and in which form in the offending case."

Date: 2021-04-20.00:00:00

P1474R1 chose to use std::to_address (a mechanism of converting pointer-like types to raw pointers) for contiguous iterators. std::to_address provides an optional customization point via an optional member in std::pointer_traits. However all iterators are not pointers, and the primary template of std::pointer_traits<Ptr> requires that either Ptr::element_type is valid or Ptr is of the form template<T, Args...> or the pointer_traits specialization is ill-formed. This requires specializing pointer_traits for those contiguous iterator types which is inconvenient for users. P1474 should have also made pointer_traits SFINAE friendly.

Date User Action Args
2021-05-10 16:30:18adminsetmessages: + msg11798
2021-04-24 17:24:50adminsetmessages: + msg11787
2021-04-20 00:00:00admincreate