Evan Rutledge Borden

@Lastalas I had considered after/beforeEach, but it just seems like a hulking mass of cruft to introduce. The others I'm not quite sure about, attaching to process seems like an...

This PR seems worth resurrecting. There are now additional stats from `base-4.14.1.0`+ tracking the non moving GC. What is pending to get this across the line. How can I help?

The newer stats are ```hs Stats.RTSStats { nonmoving_gc_sync_cpu_ns , nonmoving_gc_sync_elapsed_ns , nonmoving_gc_sync_max_elapsed_ns , nonmoving_gc_cpu_ns , nonmoving_gc_elapsed_ns , nonmoving_gc_max_elapsed_ns } ```` and ```hs Stats.GCDetails { gcdetails_nonmoving_gc_sync_cpu_ns , gcdetails_nonmoving_gc_sync_elapsed_ns } ```

My preference is, no messing with new lines and no configuration. 1. Extra whitespace or lack there of, as previously mentioned, is usually intentional. 2. Extra configuration just adds more...

I'm also heavily in favor of this feature. This would be a boon for many operator heavy use cases, like lens and DSLs.

It is worth looking at [Ormolu's handling](https://github.com/tweag/ormolu/blob/0a8cfd62eff05b092a2b99754ed6f6fa3788132b/src/Ormolu/Printer/Operators.hs). It seems Ormolu mostly side steps the fixity issue by retaining new lines. If we take the example above and format it we...

@vaclavsvejcar I have a branch with some of the work for this on it. I just haven't been able to get back to it. I'll get it back onto my...

Refreshed my old work and opened a PR over here. There is work left to do, but hopefully this gets this issue moving. https://github.com/lspitzner/brittany/pull/294

I'm also very much in support of a "compact" form of import layout. Freckle currently uses `stylish-haskell` with the following config: ```yaml - imports: align: none list_align: after_alias pad_module_names: false...

@lpil documentation of the config file is in the roadmap.