Issue 2374: [fund.ts] Remarks for optional::to_value are too restrictive

Title: [fund.ts] Remarks for optional::to_value are too restrictive
Status: open
Section: [optional.object.observe]
Submitter: Jonathan Wakely

Created on 2014-03-25.00:00:00 last changed 90 months ago

Messages

msg7049 (view)

Date: 2014-06-16.23:36:45

Proposed resolution:

This wording is relative to N3908.

Change [optional.object.observe] p23 of the Library Fundamentals specification as indicated:
```
template <class U> constexpr T value_or(U&& v) const &;
```
[…]
-23- Remarks: If ~~both constructors of T which could be selected are constexpr constructors~~the selected constructor of T is a constexpr constructor, this function shall be a constexpr function.

msg6922 (view)

Date: 2013-06-21.00:00:00

[ 2013-06-21 Rapperswil ]

Accept for Library Fundamentals TS Working Paper

msg6921 (view)

Date: 2014-03-25.22:17:25

Addresses: fund.ts

In Bristol I think I claimed that the remarks for optional::to_value() were unimplementable and the function could only be constexpr if both constructors that could be called were constexpr, but I was wrong. The remarks should be reverted to the original pre-n3793 form.

History
Date	User	Action	Args
2017-07-30 20:10:41	admin	set	status: wp -> open
2014-10-13 18:44:16	admin	set	status: immediate -> wp
2014-06-16 23:36:45	admin	set	messages: + msg7049
2014-06-16 23:36:45	admin	set	status: new -> immediate
2014-03-25 21:52:33	admin	set	messages: + msg6922
2014-03-25 00:00:00	admin	create