Mateusz Kowalczyk

So it seems to me that instances are all exported, just the way to construct some of the values aren't which would be consistent with type classes &c and therefore...

That does not seem like a ‘proof’: the instance still leaks out (just like with type classes) and Haddock even knows exactly where to find `StatementArgument`. I'd like to point...

OK, I will have a look at what GHC spits out when time allows (closer to end of the month at best unless I manage to squeeze this in somehow...

I don't think so. Trying to push forward #897 is probably anyone's best bet but I have no idea to the status of the project currently, I'm not sure if...

@alexbiehl Out of interest, what was done more concretely? The biggest issue with Haddock has always been that it has to ask GHC to re-do a lot of work, load...

I suspect it's merely the case of "patches welcome" and not something more fundamental.

Well, it doesn't display ‘nothing’, it displays all the text as it should but none of it is coloured.

>Then logging becomes a single special case, albeit one where we can provide sensible defaults. Unless there is a vast array of other cases (maybe tracing stuff? unsure) this sounds...

I did something like this, which seems like too big of a hammer as it swallows _everything_: ```haskell silently = local (\e -> e & AWS.envLogger .~ (\_ _ ->...

Likewise; having to stop using squiggly heredocs...