Closed
Description
Throughout the language part of the standard, arbitrary expressions are introduced in lower-case, .e.g:
The set of potential results of an expression
e
is defined as follows:
And arbitrary types are introduced in upper-case, e.g.:
A class type
T
must be complete if:
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]:
The expression
ranges::begin(E)
for some subexpressionE
is expression-equivalent to:
Is there a particular reason why the Ranges wording uses capital letters for expressions instead of lower-case?