Thomas Miedema

> By \\\ I meant it printed \\\\\ - I was removing the escape characters to print it literally. Ok, I was just confused for some reason. Still, it's not...

Not strictly related to this issue, but looks ok to me.

Changing `$!` to `$` in the function `beside` helps quite a bit: | input | before (s) | after (s) | | --- | --- | --- | | 100...

Fine by me. In case you know the answer, it would be great if you could add a comment or Note explaining why the other `$!`s are necessary (or a...

simonmar writes in https://ghc.haskell.org/trac/ghc/ticket/5376#comment:3: The comment worries me a bit, because it implies that when I tried this before it didn't work. Perhaps, as Brandon says, that is because the...

Note that GHC 8 will drop support for Windows XP, according to https://github.com/ghc/ghc/commit/6e6438e15f33cb94ad6338e950e693f59d046385. So I guess the suggested fix might be ok. ``` - return (cmd, translate cmd ++ "/c...

For future reference: GHC's internal copy of [pretty](https://github.com/ghc/ghc/blob/master/compiler/utils/Pretty.lhs).

I am working on making GHC's `compiler/utils/Pretty.hs` as similar as possible to `src/Text/PrettyPrint/HughesPJ.hs` from pretty-1.1.2.1 (before the annotation changes). This is a first step towards reconcillation between the two. Edit:...

Status: I don't know how to proceed. `ghc`'s version resembles `pretty-1.1.2.0`. To see the differences, do this in a ghc git tree: ``` $ cd libraries/pretty $ git checkout v1.1.2.0...

> Would supporting ByteString in Pretty be sufficient you think to provide the performance GHC needs? I guess so. @bgamari has been toying with the idea of using a different...