-
Notifications
You must be signed in to change notification settings - Fork 771
LWG-617: [sequences.general] <array> claimed to define a template meeting sequence container requirements #5916
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.
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
Comments
Why not? Reading [sequence.reqmts], it seems the intent is for it to be one, which means this is not editorial:
|
Just before the part you quoted, we have:
Thus, in context, the sentence you quoted is saying that, except for specific reasons why it isn't, |
This formulation seems wrong, because it is, according to the wording. Can you show a requirement it fails to meet? |
Just read [array.overview] paragraph 3? |
So [array.overview]p3 disagrees with [sequences.general]p1 and [sequence.reqmts]p1. |
Meeting some of the requirements does not preclude meeting all of the requirements. |
According to [sequence.reqmts]p5,
So only [sequences.general]p1 is wrong:
|
I don't think we can fix this all editorially, this probably deserves an LWG issue. (I think we probably want to make |
This was LWG-617, which I believe was incorrectly resolved NAD. |
And now it has been reopened. |
This is now LWG-617.
[sequences.general] paragraph 1 claims that
<array>
is one of various headers that define class templates that meet the requirements for sequence containers.<array>
does not define such a template.The text was updated successfully, but these errors were encountered: