From 4e94b5d413b1d80ccf29adf1ed99b709dbcc67d6 Mon Sep 17 00:00:00 2001 From: Eisenwave Date: Sun, 6 Aug 2023 21:52:00 +0200 Subject: [PATCH] [expr.cond] itemize p4 --- source/expressions.tex | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/source/expressions.tex b/source/expressions.tex index 480516076a..218099a10d 100644 --- a/source/expressions.tex +++ b/source/expressions.tex @@ -6955,12 +6955,14 @@ Using this process, it is determined whether an implicit conversion sequence can be formed from the second operand -to the target type determined for the third operand, and vice versa. -If both sequences can be formed, or one can be formed but it is the +to the target type determined for the third operand, and vice versa, +with the following outcome: +\begin{itemize} +\item If both sequences can be formed, or one can be formed but it is the ambiguous conversion sequence, the program is ill-formed. -If no conversion sequence can be formed, the operands are left unchanged +\item If no conversion sequence can be formed, the operands are left unchanged and further checking is performed as described below. -Otherwise, if exactly one conversion sequence can be formed, +\item Otherwise, if exactly one conversion sequence can be formed, that conversion is applied to the chosen operand and the converted operand is used in place of the original operand for the remainder of this subclause. @@ -6968,6 +6970,7 @@ The conversion might be ill-formed even if an implicit conversion sequence could be formed. \end{note} +\end{itemize} \pnum If the second and third operands are glvalues of the same value category