haggle: A graph library offering mutable, immutable, and inductive graphs

[ bsd3, data-structures, graphs, library ] [ Propose Tags ]

This library provides mutable (in ST or IO), immutable, and inductive graphs. There are multiple graphs implementations provided to support different use cases and time/space tradeoffs. It is a design goal of haggle to be flexible and allow users to "pay as they go". Node and edge labels are optional. Haggle also aims to be safer than fgl: there are no partial functions in the API.


[Skip to Readme]

Downloads

Maintainer's Corner

For package maintainers and hackage trustees

Candidates

Versions [RSS] 0.1.0.0, 0.1.0.1, 0.2
Change log ChangeLog.md
Dependencies base (>=4.5 && <5), containers (>=0.4), deepseq (>=1 && <2), hashable (>=1.2 && <1.5), monad-primitive (<0.2), primitive (>=0.4 && <0.9), ref-tf (>=0.4 && <0.6), vector (>=0.9 && <0.13), vector-th-unbox (>=0.2.1.3 && <0.3) [details]
License BSD-3-Clause
Author Tristan Ravitch
Maintainer tristan@ravit.ch
Category Data Structures, Graphs
Home page https://github.com/travitch/haggle
Bug tracker https://github.com/travitch/haggle/issues
Source repo head: git clone https://github.com/travitch/haggle
Uploaded by TristanRavitch at 2022-05-08T17:01:23Z
Distributions NixOS:0.2
Downloads 811 total (10 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs available [build log]
Last success reported on 2022-05-08 [all 1 reports]

Readme for haggle-0.2

[back to package description]

Overview

travis-ci status

Haggle is a graph library for Haskell. It aims to support large graphs efficiently and compactly. It differs from fgl in a few ways:

  • There are no partial functions in the API
  • There are multiple graph representations included
  • Mutable graphs can be constructed in IO or ST
  • Labels for both nodes and edges are optional

The API is based on typeclasses to allow programs to be written generically and support multiple graph representations when possible. Graphs can be mutable, immutable, or inductive.

The mutable graph support is designed to allow graphs to be efficiently constructed in a mutable context and then frozen into a pure immutable form. There are multiple representations of mutable and immutable graphs to support different use cases (simple graphs, directed graphs, and bidirectional directed graphs). The different representations allow users to make decisions on time and space tradeoffs based on their algorithmic needs.

Inductive graphs (the fgl style) are also supported, while sharing some of the API with the compact immutable graphs.

See the haddocks in Data.Graph.Haggle for information and examples on using the API.

TODO

  • Reach feature parity with the algorithms in fgl
  • Explore more graph representations
  • Explore graph serialization (the use of the opaque Vertex type makes it a bit tricky)