Open gshen42 opened 11 months ago
One interesting possibility might be Data.Compact
, though giving users the option to customize this would also be nice.
I think a design that leaves the door open to arbitrary user-provided solutions would be
LazyByteString
)ChoreoSig
requires that typeclass on the relevant constructors, and wrapper functions (eg. Cond
and cond
)Choreography.Network.Http
) perform serialization and deserialization using that typeclassThis allows a user of HasChor to implement the typeclass with Show
/Read
or Serialise
(addressing point 1 above with "don't choose", point 2 above with "don't implement", and point 4 above with "yes").
We need a better (de)serialization method than
Show
andRead
. Some questions to consider:MVar
s to communicate might not even need (de)serialization.)