RefSerialize

Write to and read from ByteStrings maintaining internal memory references

Version on this page:	0.3.1.4
LTS Haskell 20.23:	0.4.0
Stackage Nightly 2023-05-28:	0.4.0
Latest on Hackage:	0.4.0

See all snapshots RefSerialize appears in

BSD-3-Clause licensed by Alberto Gómez Corona

Maintained by agocorona@gmail.com

This version can be pinned in stack with:RefSerialize-0.3.1.4@sha256:390f3078574128f94e82ba0f97233e54f66c0a14fcb84e9c36dd52a85ee8c96e,1765

Module documentation for 0.3.1.4

Data
- Data.RefSerialize
  - Data.RefSerialize.Parser
  - Data.RefSerialize.Serialize

Depends on 6 packages(full list with versions):

base, binary, bytestring, containers, hashtables, stringsearch

Used by 2 packages in lts-3.22(full list with versions):

TCache, Workflow

Read, Show and Binary instances do not check for internal data references to the same address. As a result, the data is duplicated when serialized. This is a waste of space in the filesystem and also a waste of serialization time. but the worst consequence is that, when the serialized data is read, it allocates multiple copies for the same object when referenced multiple times. Because multiple referenced data is very typical in a pure language such is Haskell, this means that the resulting data loose the beatiful economy of space and processing time that referential transparency permits.

In this release:

Compatibility with older versions of bytestring that have no toStrict call

deserialization is much, much faster by using the stringsearch package

See Data.RefSerialize for details