Andrew Martin

Thinking about this more, I think that the direction I would prefer this to take would be to just include explicitly specialized traversals for various monads. That is, just having:...

Darn. This was a mistake. Fortunately, changing the result type from `a` to `b` is nonbreaking even for users of `TypeApplications` since GHC will infer `b` to be the last...

@winterland1989 Since opening this issue, I've actually written a different performance-oriented time library, [chronos](http://hackage.haskell.org/package/chronos). Unlike `thyme`, it is not focused on being a drop-in replacement for `time`, so it satisfies...

This would be a pretty nice feature.

> This means that anything that doesn't just cleanly map to portable ghc machine semantics is out of scope. In what way does a `Prim` instance for `Complex` or a...

I'm good with this. If there aren't any objection in the next few days, I'll merge this.

I like the stuff in the PR, although I dislike the naming convention that @treeowl suggested. I actually prefer `foldrMapPrimArray` to `foldMapRPrimArray`. Anyone else got any thoughts on the color...

I'll change the names and merge this. @Boarders Open a separate PR for a foldl on `ByteArray`. You should be able to nearly copy and paste the foldl on PrimArray.

GHC has a primop for `memset` (`setByteArray#`) that is not currently used by `primitive`. There is a [PR that switches to using this](https://github.com/haskell/primitive/pull/222). In GHC 8.10, GHC is going to...

Original issue on GHC is [here](https://gitlab.haskell.org/ghc/ghc/issues/16052) and Artem's work that resolved the issue is [here](https://gitlab.haskell.org/ghc/ghc/commit/7f33979d0160c803a215dd166d90d4e57e1f6d42).