Closed zzantares closed 1 year ago
As a consequence of c81320d8a1069674c17fa5ee52b64c18604f84de, this actually constitutes now a breaking change :thinking:
Hey! apologies for the late response, I've applied the suggestions.
BTW if this is a breaking change and brings you guys much pain then feel free to skip this if it suits you; the only thing I really needed was to actually see what was the problem I was running into.
I believe #983 will warrant Ormolu 0.6.0.0, and so we can merge this without any concerns about backwards compatibility.
When ormolu fails to parse the Cabal file the user doesn't know what is the actual error as only the cabal filepath is reported. This makes the necessary changes to actually show what errors the cabal file parser encountered.
Before:
After:
Note: Removing the
Eq
instance onOrmoluException
was the easy way to not having to implement an orphanEq
instance onPError
. This does not have any impact elsewhere as we're actually not making use of theEq
instance on this exception type.