@korkje/adt
v0.5.2
Published
Rust-inspired fancy enums for TypeScript
Downloads
68
Readme
algebraic data types
Introduction
This package attempts to bring Rust's fancy enums (and associated pattern matching) to TypeScript. These are sometimes referred to as algebraic data types, tagged unions, discriminated unions, disjoint unions, sum types, coproduct types or variant types. Read more about them here.
In Rust, you can use enums like this:
enum Ip {
V4(u8, u8, u8, u8),
V6(String),
}
let my_ip = Ip::V4(127, 0, 0, 1);
match my_ip {
Ip::V4(a, b, c, d) => println!("{}.{}.{}.{}", a, b, c, d),
Ip::V6(s) => println!("{}", s),
}
While you can't do this using enums in TypeScript, you can still take advantage of algebraic data types like so:
type Ip = {
tag: "V4";
value: [number, number, number, number];
} | {
tag: "V6";
value: string;
};
const my_ip = {
tag: "V4",
value: [127, 0, 0, 1],
} as Ip;
const assertNever = (value: never): never => {
throw new Error(`Unexpected object: ${value}`);
};
switch (my_ip.tag) {
case "V4":
const [a, b, c, d] = my_ip.value;
console.log(`${a}.${b}.${c}.${d}`);
break;
case "V6":
console.log(my_ip.value);
break;
default:
// Makes sure all cases are covered
assertNever(my_ip);
break;
}
This is both more verbose, and a lot less ergonomic. That goes for typing the ADT, instantiating variants, matching them, and making sure you've covered all cases. This package aims to solve that.
With the exported adt
and match
functions, you'll be able to achieve (among other things) the above functionality in TypeScript, like this:
import adt, { match } from "@korkje/adt";
import type { Variants } from "@korkje/adt";
const ip = adt({
v4: (a: number, b: number, c: number, d: number) => [a, b, c, d],
v6: (s: string) => s,
});
type Ip = Variants<typeof ip>;
const my_ip = ip.v4(127, 0, 0, 1) as Ip;
match(my_ip, {
v4: ([a, b, c, d]) => console.log(`${a}.${b}.${c}.${d}`),
v6: s => console.log(s),
});
This is only scratching the surface of what you can do with algebraic data types. If this sounds interesting to you, read on!
Table of contents
Installation
npm install @korkje/adt
Usage
Emulating enums
In the most simple case, adt
can be used as a drop-in replacement for TypeScript's enums:
import adt from "@korkje/adt";
const power_status = adt({
on: null,
off: null,
});
In this case, power_status
' properties are the variants of the enum. The null
primitive is used to indicate that the variant has no associated data. If you want to associate data with a variant, jump right to the fun part: beyond enums.
Useful typing
If you have a function that should return a variant, you can extract the union of the variants using the Variants
type, which is useful if you want to set an explicit return type for the function:
import type { Variants } from "@korkje/adt";
type PowerStatus = Variants<typeof power_status>;
const get_power_status = (): PowerStatus =>
Math.random() > 0.5
? power_status.on
: power_status.off;
The variants themseves are intentionally not typed as the union of all variants, which is useful in a lot of cases. For instance, you might want to implicitly narrow the return type of a function based on only the variant or variants it can return.
Matching variants
When you've got your hands on a variant, you can use the match
function to determine which one it is:
import { match } from "@korkje/adt";
const current_power_status = get_power_status();
match(current_power_status, {
on: () => console.log("The power is on"),
off: () => console.log("The power is off"),
});
Default cases
If you want, you can omit one or more cases and specify a default case instead:
const color = adt({
red: null,
green: null,
blue: null,
});
const get_color = (): Variants<typeof color> =>
// ...
match(get_color(), {
red: () => console.log("red"),
[def]: () => console.log("blue or green"),
});
As briefly mentioned above, if you don't explicitly type the return type of a function using Variants
, it will be the narrowed to only the relevant variants. Say you have a function that returns a red
or green
variant:
const get_color = () =>
Math.random() > 0.5
? color.red
: color.green;
In this case, the return type of the function is inferred as only the red or green variant, and the match
function will not expect a blue
case:
match(get_color(), {
red: () => console.log("red"),
green: () => console.log("green"),
// Not allowed:
// blue: () => console.log("blue"),
});
So, if you want to use Variants
or not will depend on your use case. You might want to ensure that all possible variants of the ADT are handled, in case your function changes in the future, or you might want to narrow the return type of the function to only the relevant variants.
Like in Rust, match
also returns the result of the function that matched the variant:
const is_on = match(current_power_status, {
on: () => true,
off: () => false,
});
Narrowing types
The return type of the match
function is the union of the return types of the functions passed to it, so using as const
can be useful for narrowing the type:
// Returns: string
match(current_power_status, {
on: () => "on",
off: () => "off",
});
// Returns: "on" | "off"
match(current_power_status, {
on: () => "on" as const,
off: () => "off" as const,
});
Beyond enums
Where TypeScript's enums are limited to encapsulating strings or numbers, adt
allows you to associate arbitrary data with variants by providing "creator" functions:
const power_status = adt({
on: (voltage: number) => voltage,
off: null,
});
The match
function can then be used to extract the data:
const U = match(current_power_status, {
on: voltage => voltage,
off: () => null,
});
The type of U
in this case is number | null
.
The variant itself is passed to the matching function as a second argument, if you need it:
const U = match(current_power_status, {
on: (_, variant) => variant,
off: () => null,
});
console.log(U.value); // 230
In this case, the type of U
is ["on", number] | null
, where ["on", number]
is the a variant with tag "on"
and value number
. More generically, the tuple [T, V]
is the internal representation a variant with tag T
and value V
. A tuple is used instead of an object (e.g. on the form { tag: T, value: V }
) simply to reduce serialization size.
As it is only the return type of the creator function that determines the type of the variant's associated data, you can get creative with it:
const power_status = adt({
on: (current: number, resistance: number) => ({
U: current * resistance,
I: current,
R: resistance,
}),
off: null,
});
const U = match(current_power_status, {
on: ({ U }) => U,
off: () => null,
});
Default with data
If you use the def
symbol to specify a default case when one or more variants have associated data, the parameter passed to the default case will be correctly typed as the union of the associated data types that don't have explicit matchers:
import adt, { match, def } from "@korkje/adt";
import type { Variants } from "@korkje/adt";
const housing = adt({
house: (floors: number, rooms: number) => ({ floors, rooms }),
apartment: (rooms: number) => number,
tent: null,
});
const get_housing = (): Variants<typeof housing> =>
// ...
match(get_housing(), {
house: ({ floors, rooms }) => console.log(`House: ${floors} floors, ${rooms} rooms`),
[def]: value => console.log(value),
});
In the above example, the type of value
(in the default matcher) will be correctly inferred as number | null
. Notice that null
is included in the inferred type, even though the tent
variant has no associated data. This is because variants with no associated data have a value of null
.
Nested ADTs
You can also nest ADTs inside one another:
const ac_status = adt({
on: (voltage: number) => voltage,
off: null,
});
type ACStatus = Variants<typeof ac_status>;
const power_source = adt({
battery: (voltage: number) => voltage,
ac: (status: ACStatus) => status,
});
type PowerSource = Variants<typeof power_source>;
const get_power_source = (): PowerSource =>
Math.random() > 0.5
? power_source.battery(12)
: power_source.ac(ac_status.on(230));
For a simple case like this, there is support for a simpler syntax:
const power_source = adt({
battery: (voltage: number) => voltage,
ac: {
on: (voltage: number) => voltage,
off: null,
},
});
type PowerSource = Variants<typeof power_source>;
const get_power_source = (): PowerSource =>
Math.random() > 0.5
? power_source.battery(12)
: power_source.ac.on(230);
However, in the following example, the simpler syntax would not work, because the ac
variant's associated data isn't only a nested ADT:
const ac_status = adt({
on: null,
off: null,
});
type ACStatus = Variants<typeof ac_status>;
const power_source = adt({
battery: (voltage: number) => voltage,
ac: (status: ACStatus, voltage: number) => ({ status, voltage }),
});
Matching nested ADTs
Using the match
function, decoding nested ADTs is a breeze:
const U = match(get_power_source(), {
battery: voltage => voltage,
ac: status => match(status, {
on: voltage => voltage,
off: () => null,
}),
});
One could envision a more concise syntax for this, in line with the simpler syntax for creating nested ADTs, but I am already stretching the capabilities of the type system (and my brain) as it is.
Anyway, something like this would be nice:
const U = match(get_power_source(), {
battery: voltage => voltage,
// Does NOT work, but would be nice:
ac: { // <-- this is the only difference
on: voltage => voltage,
off: () => null,
},
});
Going deeper
You can go as deep as you want with nested ADTs:
const activity = adt({
idle: null,
moving: {
running: {
sprinting: null,
jogging: null,
},
driving: null,
},
});
type Activity = Variants<typeof activity>;
const my_activity = activity.moving.running.sprinting as Activity;
const res = match(sprinting, {
idle: () => "idle",
moving: (mode) => match(mode, {
running: (intensity) => match(intensity, {
sprinting: () => "sprinting",
jogging: () => "jogging",
}),
driving: () => "driving",
}),
});
console.log(res); // "sprinting"
Linked list
If you want to create a more complex ADT that for instance needs to be recursive and/or generic, you could do this without using the adt
function at all:
import { variant, match } from "@korkje/adt";
type LL<T> =
| ["nil", null]
| ["cons", readonly [T, LL<T>]];
const nil = variant("nil", null);
const cons = <T>(h: T, t: LL<T>) => variant("cons", [h, t] as const);
const list: LL<number> = cons(1, cons(2, cons(3, nil)));
const ll_to_arr = <T>(ll: LL<T>): T[] => match(ll, {
nil: () => [],
cons: ([h, t]) => [h, ...ll_to_arr(t)],
});
console.log(ll_to_arr(list)); // [1, 2, 3]
Option and Result
adt
also exports two useful types: Option
and Result
. These are similar to Rust's Option
and Result
types.
Option
Option
is a type that can either be some
or none
. It is useful for representing the possibility of a value not existing.
import type { Option } from "@korkje/adt";
import { some, none } from "@korkje/adt";
const get_option = (): Option<number> =>
Math.random() > 0.5
? some(42)
: none;
const option = get_option();
const value = match(option, {
some: value => value,
none: () => null,
});
Result
Result
is a type that can either be ok
or err
. It is useful for representing the possibility of a function failing.
import type { Result } from "@korkje/adt";
import { ok, err } from "@korkje/adt";
const get_result = (): Result<number, Error> =>
Math.random() > 0.5
? ok(42)
: err(new Error("Something went wrong!"));
const result = get_result();
const value = match(result, {
ok: value => value,
err: error => {
console.error(error);
return null;
},
});
Additional helpers
if_let
if_let
is a helper function inspired by Rust's if let, that can be used to match a variant and call a function with the associated data if the variant matches:
import { if_let } from "@korkje/adt";
if_let(get_power_source(), "battery", voltage => {
console.log(`Battery voltage: ${voltage}`);
});
unwrap (and friends)
unwrap
, expect
, unwrap_or
and unwrap_or_else
are helper functions inspired by those exposed by the Option
and Result
types in Rust. Similarly, these work on the previously mentioned Option
and Result
types. The purpose of these functions is to extract the associated data from a variant, or (in some cases) to throw an error if the variant is none
or err
.
unwrap
simply extracts the associated data from a variant if it is some
or ok
, or throws an error if it is none
or err
:
import { unwrap } from "@korkje/adt";
const value = unwrap(get_option());
expect
is similar to unwrap
, but it also takes a message as its second argument, which is used to construct the error that is thrown if the variant is none
or err
:
import { expect } from "@korkje/adt";
const value = expect(get_option(), "No value!");
unwrap_or
is also similar to unwrap
, but it takes a default value as its second argument, which is returned if the variant is none
or err
:
import { unwrap_or } from "@korkje/adt";
const value = unwrap_or(get_option(), 0);
unwrap_or_else
is similar to unwrap_or
, but it takes a function as its second argument, which is used to construct the default value if the variant is none
or err
:
import { unwrap_or_else } from "@korkje/adt";
const value = unwrap_or_else(get_option(), () => 0);