Missing closing parenthesis deletes code

[i-am-the-slime]

I can't quite tell what the real issue is but I just had tidy delete a good chunk of code. The version is 0.7.1.
Funnily enough it used unsafeCoerce and tidy seemed to take this quite literally:

Here is a small Repro:

Input:

module Example where

delete me =
  unsafeCoerce (f
    (a lotta code is actually here
    )

Output:

module Example where

delete me =
  unsafeCoerce

[JordanMartinez]

Which version of purs-tidy are you on?

[thomashoneyman]

The report says it's 0.7.1, which is currently the latest version.

[JordanMartinez]

Oh, sorry, I missed that part.

[natefaubion]

@mikesol experienced this as well, but didn’t have a repro I could test. When I tested the simple missing paren case, it correctly failed with an error. Are you able to repro? Or rather is your example a true repro or just a summary of what you did?

[natefaubion]

Now that I'm able to test, the repro does indeed work. Thanks! I suspect something is up in the parser.

[natefaubion]

This is fixed in 0.7.2

[natefaubion]

The exact issue was an error in the implementation of many which propagated the wrong parser state in the case of a failure. This particular case was showing up in the call to many for expression applications. Parens and applications are a common case, but it could show up with any parse failure in any call to many.