Closed jdygert closed 1 year ago
This is indeed not intentional, but a result of the extremely simple spacing heuristic. The code simply sees the type signature and definition to not be adjacent and thus inserts an empty line. It does not realize that the space was actually filled with a comment and it's thus inserting a vertical separation that wasn't there before.
This was fixed in floskell-0.10.6
.
I'm not sure if this is intentional, but it seems unnecessary to me, and I didn't see an option to prevent this.
becomes
and
becomes
This also seems inconsistent with not having a blank line before a comment on successive patterns: