Skip to content

Commit 6b07a4d

Browse files
committed
Typos: Escaping braces meant to be code
1 parent 2f22063 commit 6b07a4d

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

specification/dartLangSpec.tex

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -22473,18 +22473,18 @@ \subsubsection{Grammatical ambiguities and clarifications}
2247322473
\paragraph{Conditional expression ambiguities}
2247422474

2247522475
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
2247822478
prefer the former parse over the latter.
2247922479

22480-
The same is true for \code{{ a is int ? - 3 : 3 }}.
22480+
The same is true for \code{\{ a is int ? - 3 : 3 \}}.
2248122481

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.
2248322483

2248422484
\paragraph{Null aware subscript}
2248522485

2248622486
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
2248822488
literal, depending on whether the \code{?} is interpreted as part of a null aware
2248922489
subscript or as part of a conditional expression. Whenever there is a sequence
2249022490
of tokens which may be parsed either as a conditional expression or as two

0 commit comments

Comments
 (0)