File tree Expand file tree Collapse file tree 1 file changed +5
-5
lines changed Expand file tree Collapse file tree 1 file changed +5
-5
lines changed Original file line number Diff line number Diff line change @@ -22473,18 +22473,18 @@ \subsubsection{Grammatical ambiguities and clarifications}
22473
22473
\paragraph{Conditional expression ambiguities}
22474
22474
22475
22475
Conditional expressions inside of braces are ambiguous between sets and maps.
22476
- That is, \code{{ a as bool ? - 3 : 3 }} can be parsed as a set literal \code{{ (a as bool)
22477
- ? - 3 : 3 }} or as a map literal \code{{ (a as bool ?) - 3 : 3 }}. Parsers will
22476
+ That is, \code{\ { a as bool ? - 3 : 3 \ }} can be parsed as a set literal \code{\ { (a as bool)
22477
+ ? - 3 : 3 \ }} or as a map literal \code{\ { (a as bool ?) - 3 : 3 \ }}. Parsers will
22478
22478
prefer the former parse over the latter.
22479
22479
22480
- The same is true for \code{{ a is int ? - 3 : 3 }}.
22480
+ The same is true for \code{\ { a is int ? - 3 : 3 \ }}.
22481
22481
22482
- The same is true for \code{{ int ? - 3 : 3 }} if we allow this.
22482
+ The same is true for \code{\ { int ? - 3 : 3 \ }} if we allow this.
22483
22483
22484
22484
\paragraph{Null aware subscript}
22485
22485
22486
22486
Certain uses of null aware subscripts in conditional expressions are ambiguous.
22487
- For example, \code{{ a?[b]:c }} can be parsed either as a set literal or a map
22487
+ For example, \code{\ { a?[b]:c \ }} can be parsed either as a set literal or a map
22488
22488
literal, depending on whether the \code{?} is interpreted as part of a null aware
22489
22489
subscript or as part of a conditional expression. Whenever there is a sequence
22490
22490
of tokens which may be parsed either as a conditional expression or as two
You can’t perform that action at this time.
0 commit comments