Open mitchellwrosen opened 3 years ago
Hi, I'm not exactly sure if this is a bug, but I observed some odd parse errors when trying to lay out some code:
First, a valid expression.
parseEcl : '{Parser} () parseEcl _ = or '(theString "amb") '(or '(theString "blu") '(theString "brn"))
If I move the arguments to the second or to a new line, it works.
or
Indenting the arguments by a single space produces this error.
parseEcl : '{Parser} () parseEcl _ = or '(theString "amb") '(or '(theString "blu") '(theString "brn")) /Users/mitchell/scratch.u:59:7: unexpected <virtual semicolon> expecting [, bang, false, handle, if, let, quote, termLink, true, tuple, or typeLink 59 | '(theString "blu") '(theString "brn"))
A second space yields a different error.
parseEcl : '{Parser} () parseEcl _ = or '(theString "amb") '(or '(theString "blu") '(theString "brn")) /Users/mitchell/scratch.u:59:7: unexpected ' 59 | '(theString "blu") '(theString "brn"))
And finally, with three or more spaces the expression becomes valid again.
This does strike me as a bug
Hi, I'm not exactly sure if this is a bug, but I observed some odd parse errors when trying to lay out some code:
First, a valid expression.
If I move the arguments to the second
or
to a new line, it works.Indenting the arguments by a single space produces this error.
A second space yields a different error.
And finally, with three or more spaces the expression becomes valid again.