Skip to content
Generation of comparison functions from types
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
expander v0.13-preview.120.26+17 Mar 6, 2019
runtime-lib v0.12-preview.120.18+252 Jan 16, 2019
src v0.12-preview.120.18+252 Jan 16, 2019
test v0.13-preview.120.36+06 May 14, 2019
.gitignore v0.13-preview.120.27+112 Mar 14, 2019 v0.11.117.09+15 May 30, 2018
Makefile v0.11.120.07+98 Oct 25, 2018
dune v0.12-preview.120.18+252 Jan 16, 2019
dune-project v0.12-preview.120.18+252 Jan 16, 2019


Generation of fast comparison and equality functions from type expressions and definitions.

Ppx_compare is a ppx rewriter that derives comparison and equality functions from type representations. The scaffolded functions are usually much faster than ocaml's and Pervasives.(=). Scaffolding functions also gives you more flexibility by allowing you to override them for a specific type and more safety by making sure that you only compare comparable values.


Type definitions: [@@deriving compare, equal] Expressions: [%compare: TYPE], [%equal: TYPE] and [%compare.equal: TYPE] Record fields: [@compare.ignore], [@equal.ignore]

Basic usage

We use ppx_deriving/ppx_type_conv, so type definitions are annotated this way:

type s = v * w [@@deriving compare]

This will generate compare_s : s -> s -> int function that relies on compare_v : v -> v -> int and compare_w : w -> w -> int.

Compare is not DWIM (do what I mean): it will scaffold a fast well behaved comparison (reflexive, transitive, symmetric...) function however it does not try to follow any "natural ordering". For instance arrays of characters are not sorted lexicographically.

Base types (options,int,array,lists,char,floats...) have the same comparison order as (provided their type parameters also do for the polymorphic ones).

Records fields are compared in the order they are defined (left to right); tuples fields are compared left to right. When we compare two branches of a sum whichever ones comes first in the definition is considered lowest. Variants compare in the order they are listed (increasing top-to-bottom). Polymorphic variants use the same ordering as the ocaml runtime.

The same applies to equality functions.

Float equality

The functions derived by [@@deriving equal] are consistent with the compare functions derived by [@@deriving compare] and in particular do not respect IEEE float comparison.

Calling compare for type ts

In compliance (or conformance) with Janestreet's coding standard we assume that type named t are the main types in a module and

type t = S.t * T.t [@@deriving compare]

will call the functions and instead of calling S.compare_t and T.compare_t. This will also generate a compare : t -> t -> int function.

The same applies to equality functions.


type t [@@deriving compare] in a module signature will add val compare : t -> t -> int in the signature.

The same applies to equality functions.

Comparison without a type definition

Sometimes you just want a comparison without having to create a new type. You can create such a comparison function using the [%compare: ..] extension point:

let gt x y = [%compare: float * int * [`A | `B | `C] ] x y

You can use the type _, in which case the corresponding values will be ignored (i.e. compared using fun _ _ -> 0). For instance:

assert ([%compare: _ list] [ true ] [ false ] = 0);
assert ([%compare: _ list] [] [ false ] <> 0);

The same applies to equality functions.

You can also check for equality using [%compare.equal: ..], which produces a function that returns true precisely when [%compare: ..] returns 0. [%equal: ..] is prefered over [%compare.equal: ..] and in particular is expected to be slightly faster. However, [%compare.equal: ..] can come in handy for types that only have [@@deriving compare]. In particular, support for [@@deriving equal] was added long after the project started, which means that many types out there only support [@deriving compare].

Special support for record fields

The comparison ignores record fields which are annotated with [@compare.ignore].

    type t =
      { a : float  [@compare.ignore]
      ; b : string
    [@@deriving compare]

The same applies for [@@deriving equal] by using [@equal.ignore]. In order to ignore a field for both comparison and equality, you can simply use [@ignore]. However, be aware that the general [@ignore] attribute will apply to any deriver that recognize it, not just compare and equal.

Note that if you use both the compare and equal derivers, you need to use either both [@compare.ignore] and [@equal.ignore] or [@ignore]. However, you cannot use only one of them.

You can’t perform that action at this time.