Skip to content

Commit ac63605

Browse files
committed
[expr.prim.req] Use grammar terms rather than undefined phrases when
referring to kinds of *requirement*.
1 parent 9d40c5a commit ac63605

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

source/expressions.tex

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1644,7 +1644,8 @@
16441644
\end{bnf}
16451645

16461646
\pnum
1647-
A simple requirement asserts the validity of an expression.
1647+
A \grammarterm{simple-requirement} asserts
1648+
the validity of an \grammarterm{expression}.
16481649
\begin{note}
16491650
The enclosing \grammarterm{requires-expression} will evaluate to \tcode{false}
16501651
if substitution of template arguments into the \grammarterm{expression} fails.
@@ -1668,7 +1669,7 @@
16681669
\end{bnf}
16691670

16701671
\pnum
1671-
A type requirement asserts the validity of a type.
1672+
A \grammarterm{type-requirement} asserts the validity of a type.
16721673
\begin{note}
16731674
The enclosing \grammarterm{requires-expression} will evaluate to \tcode{false}
16741675
if substitution of template arguments fails.
@@ -1687,7 +1688,7 @@
16871688
\end{example}
16881689

16891690
\pnum
1690-
A type requirement that names a class template specialization
1691+
A \grammarterm{type-requirement} that names a class template specialization
16911692
does not require that type to be complete~(\ref{basic.types}).
16921693

16931694
\rSec3[expr.prim.req.compound]{Compound requirements}

0 commit comments

Comments
 (0)