Oleg Grenrus

> Maybe one can simply implement the advice here, You cannot without dropping support for (at least) GHC-8.4 See https://gitlab.haskell.org/ghc/ghc/-/issues/26214

> it's not uncommon to have a test suite of 100000+ tests. I don't think that is an issue. In my opinion it would be enough to test for uniqueness...

The naming problem comes already from how to name a class: ```haskell class Traversable t => Singleton t where -- the member really should be verb... compare: traverse, map, ...,...

And FWIW, `traverseOneOf` is particularly bad name, as there is `traverse1` in the wild, which does something else what `traverseOneOf` would do, even as `optics` doesn't support `Traversable1` things. EDIT:...

Yes. I still have no idea what are the contents of the prologue. `-v3` ought to print that too if it prints e.g. contents of response files.

Lack of this feature required to split of test-suites and benchmarks from `containers`. And probably will need to do the same exercise for `time`. Also I cannot use `QuickCheck` in...

@ulysses4ever Consistent solving (picking only one *package version*) and per-component solving (picking only requested components) are orthogonal issues. Currently `cabal-install` solver solves for all components even if not all are...

Since `serialise` has written, there is RFC8949 (#279) specifying serialisation for times. Do you specifically need RFC9581 extended time support, or is https://www.rfc-editor.org/rfc/rfc8949.html#name-epoch-based-date-time enough to begin with? The full support...

Wait, there is ```haskell -------------------------------------------------------------------------------- -- Time instances -- -- CBOR has some special encodings for times/timestamps -- | 'UTCTime' is encoded using the extended time format which is currently...

I understood that motivation for this issue is compatibility issues of `serialise` with other CBOR tools in other languages. it seems that (if we fix the tag of extended time...