George Thomas

> But really this is an optparse-applicative issue Very quick response over there. Fixed and should be in the next release.

Thanks for the bug report. I've just checked and this happens with Ormolu as well, so it'd be better off being fixed upstream. Could you please [open an issue there](https://github.com/tweag/ormolu/issues)?

@parsonsmatt Could we perhaps add something to the issue template, prompting people to open issues with Ormolu when appropriate?

Sounds cool. We're pretty much open to any new options as long as they wouldn't impact future maintenance too badly. I look forward to a PR. > Alternatives: Instead of...

I don't see any particular reason to close these issues (I very much do not subscribe to the idea that a project with few open issues is necessarily a healthy...

> bikeshed: `indentation: tab` might be another way of writing this Seems preferable to me, in the usual vein of "make illegal states unrepresentable".

I'm alright with the idempotence issue seeing as: - we're fairly sure it doesn't get in to a loop - the documentation of `--column-limit` makes the issue clear (maybe it'd...

I haven't got time to go looking for the thread right now, but I *think* this was rejected for Ormolu because it would be inconsistent with function arguments. This is...

Actually, it might not be too awful for us to do this conditionally on compiler version, but I'd be a bit anxious about that.

> Would this be a welcome feature? Pretty much any feature is welcome here! Unless it would be a real pain to maintain for any reason. > Has anyone asked...