Skip to content

[expr.prim.req] Fix uses of 'unevaluated operand' #4832

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 7 additions & 5 deletions source/expressions.tex
Original file line number Diff line number Diff line change
Expand Up @@ -2694,8 +2694,6 @@
\pnum
A \grammarterm{requires-expression} is a prvalue of type \tcode{bool}
whose value is described below.
Expressions appearing within a \grammarterm{requirement-body}
are unevaluated operands\iref{term.unevaluated.operand}.

\pnum
\begin{example}
Expand Down Expand Up @@ -2779,6 +2777,7 @@
\pnum
A \grammarterm{simple-requirement} asserts
the validity of an \grammarterm{expression}.
The \grammarterm{expression} is an unevaluated operand\iref{expr.context}.
\begin{note}
The enclosing \grammarterm{requires-expression} will evaluate to \keyword{false}
if substitution of template arguments into the \grammarterm{expression} fails.
Expand Down Expand Up @@ -2848,7 +2847,9 @@

\pnum
A \grammarterm{compound-requirement} asserts properties
of the \grammarterm{expression} $E$. Substitution
of the \grammarterm{expression} $E$.
The \grammarterm{expression} is an unevaluated operand\iref{expr.context}.
Substitution
of template arguments (if any) and verification of
semantic properties proceed in the following order:

Expand Down Expand Up @@ -2957,8 +2958,9 @@
\end{example}

\pnum
A local parameter shall only appear as an unevaluated operand\iref{term.unevaluated.operand}
within the \grammarterm{constraint-expression}.
Within the \grammarterm{constraint-expression},
an \grammarterm{unqualified-id} naming a local parameter shall not be
potentially evaluated\iref{basic.def.odr}.
\begin{example}
\begin{codeblock}
template<typename T> concept C = requires (T a) {
Expand Down