Lennart Spitzner

(Just to clarify, I don't think that we need for trees-that-grow for this. In the worst case we need to write a custom equality check over the syntax tree, which...

This very likely is the same underlying issue as #242, so - this comes down to a bug in ghc-exactprint (https://github.com/alanz/ghc-exactprint/issues/79). - Does not appear wtih `ghc

Ah, this seems like a nice purely stylistic question :) and I have no strong opinion on this really. My preference leans towards the current behaviour, but the reasoning is...

We should also consider `Record{}`. Together, we currently have ~~~~.hs match Record{} = 1 match Record {..} = 2 match Record { a } = 3 match Record { a,...

The "rather big change" would be the following: ~~~~.hs match Record{} = 1 match Record{..} = 2 match Record{ a } = 3 match Record{ a, b } = 4...

Yes, I am fine with merging a PR with the layout from [#251 (comment)](https://github.com/lspitzner/brittany/issues/251#issuecomment-527611371). It seems certainly a bit more consistent than what we have at the moment. As we...

Thanks for the reproduction case. I am almost tempted to debug why exactly this happens, but this can and should best be resolved by rewriting the HsFunTy{} layouter, using the...

I approve the proposed `EPOCH.MAJOR.MINOR.POINT` versioning scheme. Even with what you mention, @scooby, I think this makes sense. We may have releases that add both a bugfix and that change...

A quick fix, just for this extension, might be to modify `ppDecl` to just ignore the `PatSynBind` node, along the lines of ~~~~.hs ppDecl :: LHsDecl RdrName -> PPMLocal ()...

Thanks for the report, need to keep track of this. I have thought about this briefly before, and I _thought_ we'd be able to transform it into `do`'s variant of...