You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This allows `x where T` to be distinguished from `x where {T}` easily
which should be quite helpful for source formatting tooling. It's also
more consistent with the other allowed (but weird) forms such as
`x where {T S}`.
Copy file name to clipboardExpand all lines: README.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -400,6 +400,7 @@ the source text more closely.
400
400
401
401
*`K"macrocall"` - allow users to easily distinguish macrocalls with parentheses from those without them (#218)
402
402
* Grouping parentheses are represented with a node of kind `K"parens"` (#222)
403
+
* The right hand side of `x where {T}` retains the `K"braces"` node around the `T` to distinguish it from `x where T`.
403
404
* Ternary syntax is not immediately lowered to an `if` node: `a ? b : c` parses as `(? a b c)` rather than `Expr(:if, :a, :b, :c)` (#85)
404
405
*`global const` and `const global` are not normalized by the parser. This is done in `Expr` conversion (#130)
405
406
* The AST for `do` is flatter and not lowered to a lambda by the parser: `f(x) do y ; body end` is parsed as `(do (call f x) (tuple y) (block body))` (#98)
0 commit comments