Skip to content

Commit 789b163

Browse files
committed
[dcl.spec.auto.general]-p2: wording on param. type
Text may be ambiguous in the sense that it may be interpreted both as the type of any of three things (incorrect) or the type of a parameter of any of three things (correct). Despite the former interpretation does not make sense as a lambda expression has never an explicit type, it would still be useful to avoid ambiguity in sentence parsing. Avoid incorrect sentence parsing option on types Signed-off-by: Mauro Russo <[email protected]>
1 parent d017ce4 commit 789b163

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

source/declarations.tex

+5-3
Original file line numberDiff line numberDiff line change
@@ -1771,9 +1771,11 @@
17711771

17721772
\pnum
17731773
The type of a \grammarterm{parameter-declaration} of a
1774-
function declaration\iref{dcl.fct},
1775-
\grammarterm{lambda-expression}\iref{expr.prim.lambda}, or
1776-
\grammarterm{template-parameter}\iref{temp.param}
1774+
\begin{itemize}
1775+
\item function declaration\iref{dcl.fct},
1776+
\item \grammarterm{lambda-expression}\iref{expr.prim.lambda},
1777+
\item \grammarterm{template-parameter}\iref{temp.param}
1778+
\end{itemize}
17771779
can be declared using
17781780
a \grammarterm{placeholder-type-specifier} of the form
17791781
\opt{\grammarterm{type-constraint}} \keyword{auto}.

0 commit comments

Comments
 (0)