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

### 2253. [arrays.ts] `dynarray` should state which container requirements aren't met

Section: 99 [arrays.ts::dynarray.overview] Status: NAD Arrays Submitter: Jonathan Wakely Opened: 2013-04-23 Last modified: 2016-10-31

Priority: 0

View all issues with NAD Arrays status.

Discussion:

Addresses: arrays.ts

99 [arrays.ts::dynarray.overview] p2 says:

> "Unless otherwise specified, all `dynarray` operations have the same requirements and semantics as specified in 99 [arrays.ts::container.requirements]."

Some differences from 99 [arrays.ts::container.requirements] are not explicitly specified, including at least the lack of a default constructor, copy assignment and `swap` member.

The wording could be similar to 24.3.7.1 [array.overview] which says "An array satisfies all of the requirements of a container and of a reversible container (99 [arrays.ts::container.requirements]), except that a default constructed array object is not empty and that `swap` does not have constant complexity."

[2013-09 Chicago:]

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

[2014-06-06 pre-Rapperswil]

This issue has been reopened as arrays-ts.

[2014-06-16 Rapperswil]

Move to Ready

[2014/11 Urbana]

Held at Ready status, pending clarification of Arrays TS

Proposed resolution:

1. Add to 99 [arrays.ts::dynarray.overview] p2:

   -2- A `dynarray` satisfies all of the requirements of a container and of a reversible container (99 [arrays.ts::container.requirements]), except for default construction, assignment and `swap`. Unless otherwise specified, all `dynarray` operations have the same requirements and semantics as specified in 99 [arrays.ts::container.requirements].