I'd say put the strict bs (cereal) and lazy bs (binary) in.<span></span><div><div><div><br>On Wednesday, August 22, 2012, Johan Tibell wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Wed, Aug 22, 2012 at 8:20 AM, Yitzchak Gale <<a href="javascript:;" onclick="_e(event, 'cvml', 'gale@sefer.org')">gale@sefer.org</a>> wrote:<br>
> Hi Johan,<br>
><br>
> Johan Tibell wrote:<br>
>> As I've mentioned before [1] I think binary and cereal should be<br>
>> merged.... [other proposed API improvements]<br>
>> 1. <a href="http://blog.johantibell.com/2011/01/merging-binary-and-cereal.html" target="_blank">http://blog.johantibell.com/2011/01/merging-binary-and-cereal.html</a><br>
><br>
> Yes, those are great ideas. The thing is, nobody<br>
> (myself included of course) has done anything about<br>
> it for almost two years. Right now, binary and cereal<br>
> are what they are. These are important packages that<br>
> are popular dependencies. I observe empirically<br>
> that their APIs are extremely stable. Unless there is<br>
> new evidence that someone will work on them in the<br>
> very near future and change the APIs significantly,<br>
> I think they should go into the platform the way they<br>
> are now. Or at least one of the two.<br>
<br>
I agree with this sentiment. My current thinking is that perhaps it's<br>
better to leave both out. I don't feel too strongly about it though.<br>
If binary went in we might convince Lennart to finish and release his<br>
"cps" branch which should give binary incremental input capabilities.<br>
<br>
-- Johan<br>
<br>
_______________________________________________<br>
Libraries mailing list<br>
<a href="javascript:;" onclick="_e(event, 'cvml', 'Libraries@haskell.org')">Libraries@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/libraries" target="_blank">http://www.haskell.org/mailman/listinfo/libraries</a><br>
</blockquote></div></div></div>