Version: 0.25.0

Unit, Option, Pattern matching

Optionals are a pervasive programming pattern in OCaml. Since Michelson and LIGO are both inspired by OCaml, optional types are available in LIGO as well. Similarly, OCaml features a unit type, and LIGO features it as well. Both the option type and the unit types are instances of a more general kind of types: variant types (sometimes called sum types).

The unit Type#

The unit type in Michelson or LIGO is a predefined type that contains only one value that carries no information. It is used when no relevant information is required or produced. Here is how it used.

In JsLIGO, the unique value of the unit type is unit.

let n : unit = unit;

Variant types#

A variant type is a user-defined or a built-in type (in case of options) that defines a type by cases, so a value of a variant type is either this, or that or... The simplest variant type is equivalent to the enumerated types found in Java, C++, JavaScript etc.

Here is how we define a coin as being either head or tail (and nothing else):

type coin = ["Head"] | ["Tail"];
let head: coin = Head();
let tail: coin = Tail();

The names Head and Tail in the definition of the type coin are called data constructors, or variants. In this particular, they carry no information beyond their names, so they are called constant constructors.

In general, it is interesting for variants to carry some information, and thus go beyond enumerated types. In the following, we show how to define different kinds of users of a system.

type id = nat;
type user =
["Admin", id]
| ["Manager", id]
| ["Guest"];
let u : user = Admin(1000 as nat);
let g : user = Guest();

In JsLIGO, a constant constructor is equivalent to the same constructor taking an argument of type unit, so, for example, Guest () is the same value as Guest (unit).

Optional values#

The option type is a predefined variant type that is used to express whether there is a value of some type or none. This is especially useful when calling a partial function, that is, a function that is not defined for some inputs. In that case, the value of the option type would be None, otherwise Some (v), where v is some meaningful value of any type. An example in arithmetic is the division operation:

let div = ([a, b]: [nat, nat]): option<nat> => {
if(b == (0 as nat)){
return (None() as option <nat>);
} else {
return (Some (a/b));
};
};

Pattern matching#

Pattern matching is similar to the switch construct in JavaScript, and can be used to route the program's control flow based on the value of a variant, record, tuple, or list.

A component of a pattern can be discarded by using a wildcard _ instead of a variable name.

LIGO will warn about unused variables bound in patterns in the same way that function arguments are warned about. Variable names beginning with _ can be used as a binder to prevent warnings.

Note: JsLIGO only supports basic pattern matching at the moment. This will change in the future.

Match on variants#

Here is a function that transforms a colour variant type to an int.

type color =
| ["RGB", [int, int, int]]
| ["Gray", int]
| ["Default"];
let int_of_color = (c : color) : int =>
match(c, {
RGB: (rgb : [int,int,int]) => 16 + rgb[2] + rgb[1] * 6 + rgb[0] * 36,
Gray: (i : int) => 232 + i,
Default: () => 0 });

Match on records or tuples#

Fields of records and components of tuples can be destructured. Record pattern variables can be renamed.

Pattern-matching on records and tuples are not supported in JsLIGO yet.

Match on lists#

let weird_length = (v : list<int>) : int =>
match(v, list([
([] : list<int>) => -1,
([hd, ...tl] : list<int>) => 1 + int(List.length(tl))
]));

Deep patterns#

Pattern matching can also be used for nested patterns.