Bikeshed the module namespace and some APIs

[well-typed]

Bikeshed the module namespace and some APIs

[adamgundry]

Just a quick observation from the trenches: it would be useful if the API exposed the "with" variants of Serialise instances, e.g.

encodeListWith :: (a -> Encoding) -> [a] -> Encoding

instead of just

defaultEncodeList :: Serialise a => [a] -> Encoding

[dcoutts]

Probably the .Class module should re-export all the useful bits of .Encoding and .Decoding that are useful for writing class instances. It should also export the class QC properties (which themselves do not depend on QC at all).

[dcoutts]

@adamgundry for what use case? For writing instances for sequence-like types?

[adamgundry]

Actually, decoding is probably a better example than encoding. I have a decoder that can't (conveniently) be a class instance, because it depends on values being passed in, which describe the generic schema of the CBOR data. But I still want to use the standard encoding/decoding functions for lists. Here's the relevant code in api-tools.

[dcoutts]

Should also decide on names, encode/decode or serialise/deserialise? The binary package uses get/put and Binary. The cereal package uses get/put and Cereal. The store package uses peek/poke and Store.

[bgamari]

Frankly I think the status quo is fine.

[bgamari]

I think we can safely close this now since the thing is released.