Section: 29.3 [numeric.requirements] Status: C++17 Submitter: Hubert Tong Opened: 2016-05-03 Last modified: 2017-07-30
View all issues with C++17 status.
In N4582 subclause 29.3 [numeric.requirements], the "considerable flexibility in how arrays are initialized" do not appear to allow for replacement of calls to the default constructor with calls to the copy constructor with an appropriate source value.
Fri AM: Moved to Tentatively Ready
This wording is relative to N4582.
Adjust 29.3 [numeric.requirements]/1 as indicated:
-1- The complex and valarray components are parameterized by the type of information they contain and manipulate. […]
(1.1) — T is not an abstract class (it has no pure virtual member functions);
(1.8) — If T is a class, its assignment operator, copy and default constructors, and destructor shall correspond to each other in the following sense: Initialization of raw storage using the default constructor, followed by assignment, is semantically equivalent to initialization of raw storage using the copy constructor. Destruction of an object, followed by initialization of its raw storage using the copy constructor, is semantically equivalent to assignment to the original object. [Note: This rule states that there shall not be any subtle differences in the semantics of initialization versus assignment. This gives an implementation considerable flexibility in how arrays are initialized. [Example: An implementation is allowed to initialize a valarray by allocating storage using the new operator (which implies a call to the default constructor for each element) and then assigning each element its value. Or the implementation can allocate raw storage and use the copy constructor to initialize each element. — end example] If the distinction between initialization and assignment is important for a class, or if it fails to satisfy any of the other conditions listed above, the programmer should use vector (23.3.11) instead of valarray for that class; — end note]