| cgi | ||
| core | ||
| examples | ||
| lwt | ||
| misc | ||
| string | ||
| tests | ||
| threads | ||
| .gitignore | ||
| .header | ||
| .merlin | ||
| .ocamlinit | ||
| _oasis | ||
| _tags | ||
| CHANGELOG.md | ||
| configure | ||
| containers.odocl | ||
| containers_misc.odocl | ||
| containers_string.odocl | ||
| LICENSE | ||
| Makefile | ||
| META | ||
| myocamlbuild.ml | ||
| README.md | ||
| setup.ml | ||
ocaml-containers
- A usable, reasonably well-designed library that extends OCaml's standard
library (in
core/, packaged undercontainersin ocamlfind. Modules are totally independent and are prefixed withCC(for "containers-core" or "companion-cube" because I'm megalomaniac). This part should be usable and should work. For instance,CCListcontains functions and lists including safe versions ofmapandappend. - A satellite library,
containers.string(in directorystring) with a few packed modules that deal with strings (Levenshtein distance, KMP search algorithm, and a few naive utils). Again, modules are independent and sometimes parametric on the string and char types (so they should be able to deal with your favorite unicode library). - Random stuff, with NO GUARANTEE of even being barely usable or tested,
in other dirs (mostly
miscbut alsolwtandthreads). It's where I tend to write code when I want to test some idea, so half the modules (at least) are unfinished or don't really work.
Some of the modules have been moved to their own repository (e.g. sequence,
gen, qcheck and are on opam for great fun and profit (or not)).
Use
You can either build and install the library (see Build), or just copy
files to your own project. The last solution has the benefits that you
don't have additional dependencies nor build complications (and it may enable
more inlining). Since modules have a friendly license and are mostly
independent, both options are easy.
If you have comments, requests, or bugfixes, please share them! :-)
License
This code is free, under the BSD license.
Documentation
The API documentation can be found here.
Contents
The design is mostly centered around polymorphism rather than functors. Such
structures comprise (some modules in misc/, some other in core/):
Core Structures
CCHeap, a purely functional heap structure.CCFQueue, a purely functional double-ended queue structureCCBV, mutable bitvectorsCCPersistentHashtbl, a semi-persistent hashtable (similar to persistent arrays)CCVector, a growable array (pure OCaml, no C) with mutability annotationsCCGenandCCSequence, generic iterators structures (with structural types so they can be defined in several places). Now also in their own repository and opam packages (genandsequence).CCKList, a persistent iterator structure (akin to a lazy list)CCList, functions on lists, including tail-recursive implementations ofmapandappendand many other thingsCCArray, utilities on arrays and slicesCCLinq, high-level query language over collectionsCCMultimapandCCMultiset, functors defining persistent structuresCCKTree, an abstract lazy tree structure (similar to whatCCKlistis to lists)- small modules (basic types, utilities):
CCIntCCString(basic string operations)CCPair(cartesian products)CCOpt(options, very useful)CCFun(function combinators)CCBoolCCOrd(combinators for total orderings)CCRandom(combinators for random generators)CCPrint(printing combinators)CCHash(hashing combinators)CCError(monadic error handling, very useful)
String
In the module Containers_string:
Levenshtein: edition distance between two stringsKMP: Knuth-Morris-Pratt substring algorithm
Misc
PHashtbl, a polymorphic hashtable (with open addressing)SplayTree, a polymorphic splay heap implementation (not quite finished)SplayMap, a polymorphic functional map based on splay treesHeap, an imperative heap based onSplayTreeGraph, a polymorphic imperative directed graph (on top ofPHashtbl)Hashset, a polymorphic imperative set on top ofPHashtblLazyGraph, a lazy graph structure on arbitrary (hashable+eq) types, with basic graph functions that work even on infinite graphs, and printing to DOT.Heap, a purely functional polymorphic heapBij, a GADT-based bijection language used to serialize/deserialize your data structuresRAL, a random-access list structure, withO(1)cons/hd/tl andO(ln(n))access to elements by their index.SmallSet, a sorted list implementation behaving like a set.AbsSet, an abstract Set data structure, a bit likeLazyGraph.Univ, a universal type encoding with affectationCache, a low level memoization cache for unary and binary functionsDeque, an imperative double ended FIFO (double-linked list)FlatHashtbl, a (deprecated) open addressing hashtable with a functorial interface (replaced by PHashtbl)UnionFind, a functorial imperative Union-Find structure.
Others
Future, a set of tools for preemptive threading, including a thread pool, monadic futures, and MVars (concurrent boxes)
Some serialisation formats are also implemented, with a streaming, non-blocking interface that allows the user to feed the input in chunk by chunk (useful in combination with Lwt/Async). Currently, the modules are:
Bencode, for the B-encode format,Sexp, for S-expressions.
There is a QuickCheck-like library called QCheck (now in its own repo).
Build
There are no dependencies (Sequence is included).
The Bij module requires OCaml >= 4.00 because of GADTs. Type:
$ make
To build and run tests (requires oUnit and qtest):
$ opam install oUnit
$ make tests
$ ./tests.native
and
$ opam install qtest
$ make qtest
To build the small benchmarking suite (requires benchmark):
$ opam install benchmark
$ make bench
$ ./benchs.native