George Thomas

Make sure to tackle #56.

@brandonchinn178 has made significant improvements to this documentation since this issue was opened. And #239 improves things further. But I still think it would be best to see nicely marked-up...

> I don't think we should use inline-ormolu, though, because people are usually confused I'm gonna go out on a limb and guess that there are just as many people...

This is cool, and I'm interested in trying it on some of my smaller personal projects. But I agree with @brandonchinn178 that more neutral language would be preferable, seeing as...

I think this might actually work best as a ternary option, with the values `always`, `never` and `detect`. Where `detect` will output unicode if and only if the `UnicodeSyntax` extension...

Is there any particular reason why this doesn't cover [all unicode syntax](https://downloads.haskell.org/~ghc/9.2.1/docs/html/users_guide/exts/unicode_syntax.html) e.g. `forall`/``∀`? I don't mind if the constructs currently implemented are the only ones you care about! But...

I see little harm in it being configurable. But I'm not that bothered either way. If someone has turned on the extension, it does seem odd for them not to...

> If you try to add Unicode syntax to a module where the extension is not enabled, there will be a parse error, so it is pointless to add an...

I have a weak preference towards the ternary option, but I don't want to bikeshed. I'm happy with no option if that's what others prefer. We can always add options...

I think we already have one or two special cases in the AST check, for differences we don't actually care about. I'd probably be happy to add leading spaces in...