
This was the motivation for the initial work on cereal. I'd be happy to see cereal make it into the HP, and I do believe that it provides a different feature set than binary, but I worry that it's reaching feature parity with attoparsec. I'm not sure what to do in the long run for this, as the two are used in fairly different ways. Maybe cereal could eventually become some sort of presentation of attoparsec and one of the builder packages? --trevor On Wed 22 Aug 2012 10:33:17 AM PDT, Johan Tibell wrote:
On Wed, Aug 22, 2012 at 10:28 AM, Bryan O'Sullivan
wrote: On Wed, Aug 22, 2012 at 9:29 AM, Johan Tibell
wrote: My current thinking is that perhaps it's better to leave both out.
For me, a disincentive to accepting binary is that it doesn't provide a way for a Get to fail. I'd be more in favour of cereal for that reason.
I switched my latest in progress package to cereal for this reason, and because I needed to incrementally supply data while parsing.
-- Johan
_______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries