Andrew Martin

It's not safe to copy the pinned bytearray backing a `ByteString`. Look at the definition of `ByteString` and `ForeignPtr`: ``` data ByteString = BS {-# UNPACK #-} !(ForeignPtr Word8) --...

If the maintainers are looking for additional maintainers to help with hackage releases and keeping the library up to date with new GHC releases, I would be happy to help.

Basically, yes. I wanted to be able to reuse the original newline characters that were present instead of reconstructing something equivalent to the original chunk. This should ultimately translate to...

If you use `uncons` or `nextByte` instead of `drop`, then your example should start working. The problem is that `drop` is intended to transform an entire stream, not to consume...

I think that defining instances for the types in `GHC.Generics` sounds reasonable. You'd need `NFData1` for some of the stuff, but all the instances seem pretty straightforward. Any of the...

Yeah, the maintenance burden is a concern. CPP is probably easier to maintain.

The GHC flag that you mention doesn’t cause any out-of-line primops to be checked. So, copyByteArray can still corrupt memory. There’s a debug version of the GHC runtime that adds...

Additionally, the GHC option causes an error that includes no information about the index or the length of the array. The approach in this PR provides that information in the...

I've been mulling over an approach that reifies the dictionary instead of passing it around as a class constraint. I think this would permit base monads other than `IO` and...

I spent some time this weekend trying to explore this space further, and I cannot come up with anything easy to reason about that makes types like `Maybe`, `Identity`, and...