Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[sequence.reqmts] Table "Sequence container requirements" is bad, and it should feel bad #120

Closed
sdutoit opened this issue May 12, 2013 · 0 comments · Fixed by #4460
Closed

[sequence.reqmts] Table "Sequence container requirements" is bad, and it should feel bad #120

sdutoit opened this issue May 12, 2013 · 0 comments · Fixed by #4460

Comments

@sdutoit
Copy link
Contributor

sdutoit commented May 12, 2013

This table uses ugly shorthand for pre/postconditions, like so:

Requires: T shall be [...]
post: distance(begin(), end()) == distance(i, j)

It also misses \effects clauses, e.g.:

Requires : T shall be [...]
pre: i and j are not iterators into a.
Inserts copies of elements in [i, j) before p
redboltz pushed a commit to redboltz/draft that referenced this issue Aug 6, 2014
LWG2231 DR 704 removes complexity guarantee for clear()
6dc471d 
General issues with this table logged at
cplusplus#120
@jensmaurer jensmaurer mentioned this issue Jan 7, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Dismantle requirements table in [re.req] and [container.requirements] jensmaurer/draft
1 participant
@sdutoit