-
Notifications
You must be signed in to change notification settings - Fork 767
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
Upper-case vs Lower-case for expressions #3271
Comments
[algorithms] uses "Let @CaseyCarter, any opinion here? |
IIRC [algorithms] inconsistently used both I have a mild preference for |
The general idea for |
Editorial meeting:
Deferring. |
Editorial meeting: Use math variables for everything, including types. |
Throughout the language part of the standard, arbitrary expressions are introduced in lower-case, .e.g:
And arbitrary types are introduced in upper-case, e.g.:
Both of those are from [basic.def.odr], but it's consistent throughout the language section.
Much of the new library wording from Ranges breaks this convention by introducing expression in upper-case in all the definitions of the CPOs. For instance, from [range.access.begin]:
Is there a particular reason why the Ranges wording uses capital letters for expressions instead of lower-case?
The text was updated successfully, but these errors were encountered: