data-reify

Reify a recursive data structure into an explicit graph.

http://ku-fpg.github.io/software/data-reify/

Version on this page:0.6.3
LTS Haskell 23.4:0.6.4
Stackage Nightly 2025-01-14:0.6.4
Latest on Hackage:0.6.4

See all snapshots data-reify appears in

BSD-3-Clause licensed by Andy Gill
Maintained by Andy Gill
This version can be pinned in stack with:data-reify-0.6.3@sha256:eae99d1731cb20e65be6bb5d46e89469d8d73e277abaeaebb30526b518bccb7d,4333

Module documentation for 0.6.3

Used by 3 packages in lts-18.8(full list with versions):
ad, data-reify, folds

data-reify Hackage version Build Status

data-reify provided the ability to turn recursive structures into explicit graphs. Many (implicitly or explicitly) recursive data structure can be given this ability, via a type class instance. This gives an alternative to using Ref for observable sharing.

Observable sharing in general is unsafe, so we use the IO monad to bound this effect, but can be used safely even with unsafePerformIO if some simple conditions are met. Typically this package will be used to tie the knot with DSLs that depend of observable sharing, like Lava.

Providing an instance for MuRef is the mechanism for allowing a structure to be reified into a graph, and several examples of this are provided.

History: Version 0.1 used unsafe pointer compares. Version 0.2 of data-reify used StableNames, and was much faster. Version 0.3 provided two versions of MuRef, the mono-typed version, for trees of a single type, and the dynamic-typed version, for trees of different types. Version 0.4 used Int as a synonym for Unique rather than Data.Unique for node ids, by popular demand. Version 0.5 merged the mono-typed and dynamic version again, by using DynStableName, an unphantomized version of StableName.

Changes

0.6.3 [2020.10.12]

  • Fix a bug introduced in data-reify-0.6.2 where reifyGraph could return Graphs with duplicate key-value pairs.

0.6.2 [2020.09.30]

  • Use HashMaps and IntSets internally for slightly better performance.

0.6.1

  • Fix warnings in GHC 7.10.

0.5

  • Merge the mono-typed and dynamic version again, by using ‘DynStableName’, an unphantomized version of StableName.

0.4

  • Use ‘Int’ as a synonym for ‘Unique’ rather than ‘Data.Unique’ for node ids, by popular demand.

0.3

  • Provide two versions of ‘MuRef’, the mono-typed version, for trees of a single type, and the dynamic-typed version, for trees of different types.

0.2

  • Use ‘StableName’s, making data-reify much faster.

0.1

  • Use unsafe pointer compares.