Brandon Chinn

Perfect, thanks! Can you follow the instructions in CONTRIBUTING.md to update docs + tests for your new option?

Sorry, DEVELOPER.md

That makes sense to me! Have you checked to see if this is something Ormolu wants? If so, it would be better to make the change upstream instead.

> I see little harm in it being configurable. That's fair. I think this is something Ormolu would be interested in anyway, so I think we should wait and see...

Personally, I dont think we need any option. If someone wants to disable it for a particular module, they can turn off the extension with NoUnicodeSyntax

Also, it looks like there are test failures. The biggest one being that `fourmolu.yaml` should be updated to include `unicode: never` (being that `fourmolu.yaml` represents the configuration to match ormolu's...

Yes, that's correct. One way to look at this is if you have some code ```hs foo :: ... foo = ... -- some comment here bar :: ... bar...

The initial bug reported here is fixed with https://github.com/fourmolu/fourmolu/pull/173. Indeed, running the two examples above with `fourmolu 0.7.0.1` works now. I'll be closing this issue. @lf- thanks for the report,...

ref: * https://github.com/pcapriotti/optparse-applicative/issues/406 * https://github.com/pcapriotti/optparse-applicative/issues/258 * https://github.com/pcapriotti/optparse-applicative/pull/407 Fixed in optparse-applicative 0.17

Sorry, it seems like optparse-applicative 0.17 will just make it configurable. Reopening to fix the help text after optparse-applicative 0.17 is released https://github.com/pcapriotti/optparse-applicative/issues/443