Phil Hazelden

Hm. To be precise, I think that if `gpow` or `ginvert` used `mappend`, then this change wouldn't *break compilation* of `groups-generic`, but would *change behavior*, right? Because if I do...

Wait, I spoke too soon. The [default definition](https://hackage.haskell.org/package/groups-0.5.3/docs/src/Data.Group.html#pow) of `pow` does use `mappend`. So I think this does have that effect. But to be clear, it doesn't change behavior for...

> I am hard pressed to think of an example where it makes sense to separate the `Monoid (Generically a)` mappend from the semigroup's `()`; perhaps I have not worked...

Oh, good catch. It would be a shame to make it harder to move `mappend` out of `Monoid`. Your proposal doesn't say much explicitly about `Monoid`, just says it would...

As far as I'm concerned, no apology needed. The two proposals interact and it's important to realize that. > A question on this issue: if `mappend` is not defined for...

No, if we don't define `mappend` for `Generically a` then we get `mappend = ()` using the `` from `Semigroup (Generically a)`, equivalent to the current definition. Downstream instances can't...

Hm, yeah. I can't offhand think of a *sensible* way this could be violated without things like `mappend` and `return` that shouldn't really exist. But here's a silly way: ```haskell...

I regularly run into situations where it makes a big practical difference to performance :p Like, it can be several minutes versus a few seconds. But also, it can really...

> It's gone now, see screens, but we could bring it back. Oh, right. My inclination would be to leave it, or at any rate not to disable it along...

So I'd still be happier if there's some way (e.g. environment variable) to get the full reproduce message when using hspec-hedgehog. There's a question in my mind of whether that...