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.

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

revise section labels introduced by ranges #2513

Closed
zygoloid opened this issue Nov 26, 2018 · 3 comments
Closed

revise section labels introduced by ranges #2513

zygoloid opened this issue Nov 26, 2018 · 3 comments
Assignees

Comments

@zygoloid
Copy link
Member

In particular, [range] should be [ranges] for consistency with the rest of the library. There are probably other opportunities for cleanups here.

@jensmaurer jensmaurer self-assigned this Nov 26, 2018
@jensmaurer
Copy link
Member

jensmaurer commented Nov 26, 2018

We consistently have [range.foo.bar] for subclauses. @zygoloid, do you want them renamed to [ranges.foo.bar] as well?

@zygoloid
Copy link
Member Author

Use your judgment for the subclause labels. [range.general] should be renamed, but [range.access], [range.primitives], etc seem fine as-is to me. Maybe [range.range] should be [ranges.range].

@jensmaurer
Copy link
Member

Thanks. Most labels look reasonable, but there are some very long ones that I'd like to shorten. E.g. "iterator" -> "iter" and "operations" -> "op"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants