Chris Done

> This is the bug that keeps me from adopting hindent Nobody is stopping you from going fixing it. Are you a Haskeller or not?

I must have misunderstood the tone of your original comment, my apologies.

I've gotten used to the more regular way of formatting operators at the end of the line, but I'm fine with adding specific support for these operators to be formatted...

Good point regarding the horizontal movement. The suggested above one causes dependency on the length of the name `Opts` which isn't ideal. Can anyone suggest an alternative layout? Perhaps: ```...

Here is probably why: https://github.com/chrisdone/hindent/blob/master/src/main/Path/Find.hs#L59

Either `F{...}` or `(F {...})` seem reasonable to me objectively speaking. Stylistically I have no preference.

Neil Mitchell said that he just memory maps the file. Perhaps you could try that and report back? https://hackage.haskell.org/package/mmap-0.5.9/docs/System-IO-MMap.html#v:mmapFileByteString

I'd be interested to know the speed of it.

~~By the way, the [sax](https://hackage.haskell.org/package/sax) package is a streaming parser implemented using `xeno`. So that might be an option if you want to stream.~~ Wrong, see below.

> A quick-and-dirty speed comparison shows process print (\_ _ -> return ()) c c c c where c = (\_ -> return ()) taking 12s on a 1G file,...