ANNOUNCE: cereal-0.3.3.0

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

ANNOUNCE: cereal-0.3.3.0

Trevor Elliott-3
Hot on the heels of the last release, cereal-0.3.3.0 [1] adds support
for parsing and rendering lazy ByteStrings.  Most running functions in
Data.Serialize.Get and Data.Serialize.Put now have lazy analogues, and
Data.Serialize has gained encodeLazy and decodeLazy.

This new functionality was made possible by the incremental parsing
support added in cereal-0.3.1.0 by Lemmih.

[1] http://hackage.haskell.org/package/cereal-0.3.3.0


_______________________________________________
Haskell-Cafe mailing list
[hidden email]
http://www.haskell.org/mailman/listinfo/haskell-cafe

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: ANNOUNCE: cereal-0.3.3.0

Vo Minh Thu
2011/4/26 Trevor Elliott <[hidden email]>:
> Hot on the heels of the last release, cereal-0.3.3.0 [1] adds support
> for parsing and rendering lazy ByteStrings.  Most running functions in
> Data.Serialize.Get and Data.Serialize.Put now have lazy analogues, and
> Data.Serialize has gained encodeLazy and decodeLazy.
>
> This new functionality was made possible by the incremental parsing
> support added in cereal-0.3.1.0 by Lemmih.

Hi,

For lazy ByteStrings, what would be the reason to prefer cereal or binary now?

Thanks,
Thu

_______________________________________________
Haskell-Cafe mailing list
[hidden email]
http://www.haskell.org/mailman/listinfo/haskell-cafe
Reply | Threaded
Open this post in threaded view
|

Re: ANNOUNCE: cereal-0.3.3.0

Trevor Elliott-3
You might still prefer to use binary if your goal is to stream parsed
data.  Using cereal, this takes a bit more work.

--trevor

On 04/27/2011 12:17 AM, Vo Minh Thu wrote:

> 2011/4/26 Trevor Elliott <[hidden email]>:
>> Hot on the heels of the last release, cereal-0.3.3.0 [1] adds support
>> for parsing and rendering lazy ByteStrings.  Most running functions in
>> Data.Serialize.Get and Data.Serialize.Put now have lazy analogues, and
>> Data.Serialize has gained encodeLazy and decodeLazy.
>>
>> This new functionality was made possible by the incremental parsing
>> support added in cereal-0.3.1.0 by Lemmih.
>
> Hi,
>
> For lazy ByteStrings, what would be the reason to prefer cereal or binary now?
>
> Thanks,
> Thu
>

_______________________________________________
Haskell-Cafe mailing list
[hidden email]
http://www.haskell.org/mailman/listinfo/haskell-cafe

smime.p7s (4K) Download Attachment