Title
Refer back to container requirements when extending them
Status
new
Section
[containers]
Submitter
Jonathan Wakely

Created on 2024-11-22.00:00:00 last changed 3 days ago

Messages

Date: 2025-02-15.00:00:00

[ 2025-02-07; Reflector poll ]

Set priority to 4 after reflector poll.

Date: 2024-11-22.00:00:00

We sometimes give detailed specifications of container members which add additional specification to the common requirements in [container.requirements.general], for example [vector.modifiers] defines `vector::erase` without actually saying it erases any elements. The actual effects of `erase` are given in [sequence.reqmts].

Authors of library wording often struggle with this non-local form of specification, where we sometimes do spell out container member functions in full, and sometimes rely on distant wording that applies to all containers. It would be easier if `vector::erase` referred back to [sequence.reqmts].

History
Date User Action Args
2025-02-07 20:50:56adminsetmessages: + msg14590
2024-11-22 00:00:00admincreate