Issue 2282: [fund.ts] Incorrect is_assignable constraint in optional::op=(U&&)

Created on 2013-08-25.00:00:00 last changed 119 months ago

msg7057 (view)

Date: 2014-06-17.08:47:43

Proposed resolution:

This wording is relative to N3691.

Edit [optional.object.assign] p15 as indicated:
```
template <class U> optional<T>& operator=(U&& v);
```
-15- Requires: is_constructible<T, U>::value is true and is_assignable<U, TT&, U>::value is true.

msg7005 (view)

Date: 2014-06-16.00:00:00

[ 2014-06-16 Rapperswill ]

Confirmed that this issue is resolved in the current Library Fundamentals working paper.

msg6994 (view)

Date: 2014-06-07.00:00:00

[ 2014-06-07 Daniel comments ]

This issue should be set to Resolved, because the wording fix is already applied in the last fundamentals working draft.

msg6631 (view)

Date: 2014-06-06.00:00:00

[ 2014-06-06 pre-Rapperswill ]

This issue has been reopened as fundamentals-ts.

msg6570 (view)

Date: 2014-06-06.21:18:30

[ 2013-09 Chicago: ]

Move to Deferred. This feature will ship after C++14 and should be revisited then.

msg6569 (view)

Date: 2014-06-06.21:18:30

Addresses: fund.ts

Minor wording nit in [optional.object.assign]/p15:

template <class U> optional<T>& operator=(U&& v);
-15- Requires: is_constructible<T, U>::value is true and is_assignable<U, T>::value is true.

Should be:

template <class U> optional<T>& operator=(U&& v);
-15- Requires: is_constructible<T, U>::value is true and is_assignable<T&, U>::value is true.