Tablecloth is an ergonomic, cross-platform, standard library for use with OCaml
and ReasonML. It provides an easy-to-use, comprehensive and performant standard
library, that has the same API on all OCaml/ReasonML/Bucklescript platforms.
Tablecloth is alpha-quality software, and is pre-1.0. The API will change
over time as we get more users. Caveat emptor.
See the mli for documentation.
Install via npm by:
npm install tablecloth-bucklescript
Then add to your bsconfig.json file:
"bs-dependencies" : ["tablecloth-bucklescript"]
Install via opam:
opam install tablecloth-native
Then add to your dune file:
(libraries (tablecloth-native ...))
We have not built a js_of_ocaml specific version yet. However, the native version should work perfectly with js_of_ocaml.
By design, the usage of the libraries is the same on all platforms:
Either open the module, and replace the builtin modules
open Tablecloth let () = "somestring" |> String.toList |> List.map ~f:Char.toCode |> List.map ~f:(fun x -> x+1) |> List.map ~f:Char.fromCode |> String.fromList
Or use the fully qualified names:
let () = "somestring" |> Tablecloth.String.toList |> Tablecloth.List.map ~f:Char.toCode |> Tablecloth.List.map ~f:(fun x -> x+1) |> Tablecloth.List.map ~f:Char.fromCode |> Tablecloth.String.fromList
As tablecloth is still in the early stages, you might find it useful to create
a module wrapping tablecloth, that allows you make changes to it before
upstreaming them. We have an
that you can copy from.
Design of Tablecloth
Dark uses multiple versions of OCaml on the frontend
Our backend is written in OCaml native, using Jane Street Core as a standard
Parts of our backend are shared with the frontend by compiling them using
js_of_ocaml, and running them in a web worker.
We discovered that it was impossible to share code between the Bucklescript
frontend and the native OCaml backend, as the types and standard libraries were
Bucklescript uses camelCase by default, while most native libraries,
including Core and the OCaml standard library, use snake_case.
The libraries in Belt have different names and function signatures than native OCaml and Base/Core.
Many OCaml libraries have APIs optimized for pipelast (
|>), while Belt aims
for pipefirst (
Core does not work with Bucklescript, while Belt is optimized for the JS
Belt does not work in native OCaml, while Core is optimized for the native
Belt is incomplete relative to Core, or to other languages' standard
libraries (such as Elm's).
Belt makes it challenging to use PPXes.
Tablecloth solves this by providing an identical API for Bucklescript and
OCaml. It wraps existing standard libraries on those platforms, and so is fast
and memory efficient. It is based off the Elm standard library, which is extremely
well-designed and ergonomic.
Tablecloth provides separate libraries for OCaml native/js_of_ocaml and
Bucklescript. The libraries have the same API, but different implementations,
and are installed as different packages.
are taken from Elm's standard library, which is extremely complete and well-designed.
include support for strings, lists, numbers, maps, options, and results,
have both snake_case and camelCase versions of all functions and types,
are backed by Jane Street Base for native OCaml
are backed by Belt and the
Jslibrary for Bucklescript/ReasonML,
use labelled arguments so that can be used with both pipefirst and pipelast,
are well documented, and reasonably-well tested.
We also have design goals that are not yet achieved in the current version:
Many of the functions in the Bucklescript version were written hastily, and could be much more efficient
Tablecloth libraries should support PPX derivers,
Tablecloth functions should not throw any exceptions,
All functions should have well-known and consistent edge-case behaviour,
Tablecloth is an ideal library to contribute to, even if you're new to OCaml or
new to writing algorithms. The maintainers are warm and friendly, and the
project abides by a Code of Conduct. There are many
small tasks to be done - a small change to a single function can be extremely
Here are some ways to contribute:
point out inconsistencies between different functions in the library,
point out an inelegant function signature which could be improved,
point out a way in which the library or any of its parts are confusing,
report an edge-case or performance problem in one of the functions,
add a small test for an edge-case of one of the functions,
copy test cases for a function from another language's standard library,
add documentation to a function,
improve a function's documentation by discussing an edge-case,
check that a function cannot throw exceptions (and add a note to the function
documentation to that effect),
optimize a function (the Bucklescript functions in particular),
write a benchmark for a function, or a set of functions,
make a plan for the addition (or not) of U-suffixed functions like in Belt,
make a plan for adding polymorphic Maps and Sets,
design a Regex module,
design escape hatches, where the user could convert a
platform-specific type, to allow them create functions we do not currently
add more functions from any of Elm's core library: String, List, Result,
Maybe, Array, Dict, Set, Tuple, or Basics, or from any of the Extras
If you are new to OCaml there are a few prerequisites you will
need to get started:
Install OCaml and OPAM based on your OS
You may need to run
For Bucklescript install a current version of Node
Please refer to the
Makefile for a complete list of supported actions. Here is
a handful of useful, supported commands:
make deps-native: Install native dependencies.
make deps-bs: Install bs dependencies.
make build: Build the project.
make test: Run the test suite. You may need to
make documentation: Build the documentation to browse offline.