Title
Should the Standard Library use explicit only when necessary?
Status
lewg
Section
[containers]
Submitter
Zhihao Yuan

Created on 2013-09-26.00:00:00 last changed 74 months ago

Messages

Date: 2018-11-12.05:21:03

[ 2018-11 San Diego Thursday night issue processing ]

LEWG has rejected Nevin's paper, so they need to formulate a policy.

Date: 2018-08-22.12:55:05

[ 2018-08 Batavia Monday issue discussion ]

This really needs a paper; splitting a lot of constructors. Nevin to write paper.

Date: 2014-11-08.16:43:57

[ Urbana 2014-11-07: Move to Open ]

Date: 2013-09-26.00:00:00

LWG 2193 yields explicit for default ctors to allow {}, but not for all cases of uniform initialization. For example:

explicit vector(size_type count, const Allocator& alloc = Allocator());

This prevents {n, alloc()}. Although this use is relatively rare, but the behavior is inconsistent with that of

vector(size_type count, const T& value, const Allocator& alloc = Allocator());
History
Date User Action Args
2018-11-12 05:21:03adminsetmessages: + msg10210
2018-11-12 05:21:03adminsetstatus: open -> lewg
2018-08-22 12:55:05adminsetmessages: + msg10090
2014-11-08 16:43:57adminsetmessages: + msg7170
2014-11-08 16:43:57adminsetstatus: new -> open
2013-09-26 00:00:00admincreate