Repository navigation
Excessive parser backtracking in lambda arguments #3262
Description
Activity
A smaller example:
foo = id \a -> [1,,2]\is a valid operator, so maybe since the lambda body parse failed, it's backtracking to parseid \ a. I think since the lambda head is correct, it should be able to commit, since->is not a valid operator.I think this is anything that causes backtracking to
Parsec.buildExpressionParser.bad = id [,]Unable to parse module: unexpected [This example should clearly fail with an unexpected
,instead, which you'd get if you left off theid.I think this is safe to close unless we want to add tests for error positions, but that might be more effort than it's worth.
http://try.purescript.org/?backend=core&gist=40b83a8631b49dfb1cc7584aaea0fb1d
If you remove
idthen there is a sensible error position.