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

[iterator.container,range.prim] "range" vs. "container and/or view" #2614

Closed
CaseyCarter opened this issue Dec 21, 2018 · 1 comment
Closed

[iterator.container,range.prim] "range" vs. "container and/or view" #2614

CaseyCarter opened this issue Dec 21, 2018 · 1 comment
Assignees
@jensmaurer

Comments

@CaseyCarter
Copy link
Contributor

Could we editorially merge [iterator.container] into [iterator.range], and likewise merge [range.prim] into [range.access]? I defy anyone to explain to me the difference between "range" and "container and/or view".

Should I simply prepare a PR to do so, and we can decide on the basis of the proposed wording changes whether or not the change needs LWG approval?
@jensmaurer
Copy link
Member

Both changes sound good to me; please prefix the subclause headings in [range.prim] and [iterator.container] with ranges:: for consistency with the respective receiving subclause. Feel free to prepare a pull request.

@jensmaurer jensmaurer self-assigned this Dec 29, 2018
@jensmaurer jensmaurer mentioned this issue Dec 29, 2018
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jensmaurer jensmaurer

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@CaseyCarter @jensmaurer