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

### 3627. Inconsistent specifications for `std::make_optional` overloads

Section: 20.6.9 [optional.specalg] Status: New Submitter: Jiang An Opened: 2021-10-23 Last modified: 2021-10-24

Priority: 3

View all issues with New status.

Discussion:

Three `std::make_optional` overloads are specified in 20.6.9 [optional.specalg]. The first one is specified by "Returns:" and the other two are specified by "Effects: Equivalent to:". According to 16.3.2.4 [structure.specifications]/4, such uses of "Effects: Equivalent to:" propagate the Constraints specified for constructors. As the selected constructor for the first overload has "Constraints:" (20.6.3.2 [optional.ctor]/22), it seems that inconsistency is introduced here.

Existing implementations are inconsistent: libstdc++ constrains all three overloads, while libc++ and MSVC STL do not constrain any of them.

IMO all three overloads should be constrained.

[2022-01-29; Reflector poll]

Set priority to 3 after reflector poll.

Proposed resolution:

This wording is relative to N4901.

1. Modify 20.6.9 [optional.specalg] as indicated:

   >     template<class T> constexpr optional<decay_t<T>> make_optional(T&& v);

   > > -3- Returns Effects: Equivalent to: `return optional<decay_t<T>>(std::forward<T>(v));`.