A freer-monad effect layer in pure Nix, with a dependent type checker on top of it.
Validation is a typeCheck effect. A validator walks a nested record
and sends typeCheck at every leaf; the handler decides what happens
on failure:
# src/effects/typecheck.nix — three handlers for the same effect.
strict = {
typeCheck = { param, state }:
if param.type.check param.value
then { resume = true; inherit state; }
else builtins.throw
"Type error in ${param.context}: expected ${param.type.name}, got ${builtins.typeOf param.value}";
};
collecting = {
typeCheck = { param, state }:
if param.type.check param.value
then { resume = true; inherit state; }
else {
resume = false;
state = state ++ [{
context = param.context;
typeName = param.type.name;
actual = builtins.typeOf param.value;
message = "Expected ${param.type.name}, got ${builtins.typeOf param.value}";
}];
};
};
logging = {
typeCheck = { param, state }:
let passed = param.type.check param.value;
in { resume = passed;
state = state ++ [{
context = param.context;
typeName = param.type.name;
inherit passed;
}]; };
};The same validator runs under all three without a rewrite. strict
throws on the first bad field. collecting visits every leaf and
returns the failures with their context paths. logging records
every check, pass or fail — how you debug a validator that rejects a
value you thought it should accept.
The dependent type checker in src/tc/ is ordinary pure Nix — no
fx.* calls — but .validate routes through typeCheck, so type
errors in deeply nested terms come back with the field path that
broke.
Recursion in the kernel and the effect interpreter goes through a
trampoline built on builtins.genericClosure (Nix's only iterative
primitive) with deepSeq on the dedup key to break thunk chains. Call
stack stays O(1); 1M operations evaluate in roughly 3 seconds. See
book/src/trampoline.md.
Everything runs at nix eval time.
- Freer monad with FTCQueue — O(1)
bindvia catenable queue snoc (Kiselyov & Ishii 2015) - Trampolined interpreter — O(1) call-stack depth built on
builtins.genericClosurewithdeepSeq-broken thunk chains; 100k operations in the test suite, 1M in ~3s manually - Handler semantics —
resume/abortfollowing Plotkin & Pretnar (2009); handlers may return a computation as theirresumeand have its effects spliced into the pending continuation - Selective handler rotation (
fx.rotate) — handles matching effects and forwards unknown ones outward (Kyo-style lawhandle(t1, suspend(t2, i, k), f) = suspend(t2, i, x → handle(t1, k(x), f))) - Scoped handlers (
fx.effects.scope) —run,runWith, andstatefulinstall handlers over a subcomputation with optional state hiding - State composition via lenses —
fx.adaptandfx.adaptHandlerslift handlers over component state into handlers over parent state - Built-in effects —
state,reader,writer,acc(accumulation),choice(nondeterminism),error,conditions(Common-Lisp-style restarts),typecheck(blame-tracking validation),linear(graded linear resource tracking) - Streams — effectful lazy sequences with
map,filter,take,takeWhile,fold,scanl,zip,zipWith,interleave, etc.
- Primitives —
String,Int,Bool,Float,Attrs,Path,Function,Null,Unit,Any - Compound types —
Record,ListOf,Maybe,Either,Variant,Vector - Dependent types —
Pi(dependent function),Sigma(dependent pair),DepRecord,Certified(Σ with a Boolean witness — see Known limitations) - Identity types with
Jelimination —sym,trans,cong,transportderived fromJ;Reflas the sole introduction form - Inductive types via a description universe —
Descandμas kernel primitives;Nat,List,Sum, andUnitrebuilt as HOAS descriptions on top, so further inductives don't require kernel changes - Datatype macro layer — declare single- or multi-constructor
datatypes directly in HOAS with
datatype/datatypeP+field,fieldD,piField,piFieldD,recField. Dependent fields see prior fields by name (prev.op,prev.comp), poly parameters thread through aparamPibinder. Chains of saturated or linear-recursive constructors flatten to flatdesc-conterms at elaboration time, so 5000-element lists type-check without blowing the stack.Nat,List, andSumare themselves built through the macro; user datatypes use exactly the same surface (seeapps/category-theory/for a guided tour) - Refinement types — narrow any type with a predicate;
combinators
allOf,anyOf,negate; helperspositive,nonNegative,inRange,nonEmpty,matching(Freeman & Pfenning 1991; cf. Rondon et al. 2008) - Linear/Affine/Graded types — resource tracking with exact, ≤-bounded, or =k-bounded usage counts
- Cumulative universes —
Type_0 .. Type_4(andtypeAt nfor any n), level computed from typing derivation for kernel-backed types - Bidirectional type checking with NbE — normalization by evaluation,
check/infersplit, HOAS elaboration (Dunfield & Krishnaswami 2021) - Proof terms and verified extraction —
fx.types.hoascombinators build proof terms;fx.types.extractandverifyAndExtractproduce plain Nix callables from verified HOAS bodies - Polarity-aware elaboration — positive types (Sigma, Sum, Nat)
elaborate structurally; negative types (Pi) elaborate opaquely with
a domain-check trust boundary (
mkOpaqueLam) - Typecheck effect with blame context —
.validatesendstypeCheckeffects carrying a path-qualifiedcontextfield, so the same validator runs under strict, collecting, or logging handlers without rewriting
- Category theory library (
apps/category-theory/) — a guided tour of the MLTT kernel and the datatype macro layer. Five chapters that build on each other:combinators.nix—sym/trans/congderived fromJ.arithmetic.nix—addonNatwith seven verified properties including commutativity.algebra.nix—MonoidandCategoryas macro-generated datatypes (single-constructor, named fields, dependent law fields); instancesnatAddMonoidandnatCategory; the theorem that composition innatCategoryis commutative, stated throughnatCategory.comp.functor.nix—MonoidHomandFunctoras two more macro datatypes; the doubling map packaged as both a monoid homomorphism (doubleHom) and an endofunctor onnatCategory(doubleFunctor), showing the same map through two lenses.yoneda.nix— Yoneda's lemma as an equivalence of types, with both round-trip proofs (by J-based path induction).
- Expression interpreter and build simulator (
apps/interp/,apps/build-sim/) — effect-layer benchmarks at scale
Add nix-effects as a flake input:
{
inputs.nix-effects.url = "github:kleisli-io/nix-effects";
outputs = { nix-effects, ... }:
let fx = nix-effects.lib;
in {
# Use fx.types, fx.run, fx.send, fx.bind ...
};
}Or import directly (non-flake):
let
pkgs = import <nixpkgs> {};
fx = import ./path/to/nix-effects { lib = pkgs.lib; };
in ...To also get benchmark runner derivations (fx.bench.run, fx.bench.compare),
pass pkgs:
let
pkgs = import <nixpkgs> {};
fx = import ./path/to/nix-effects { inherit pkgs; lib = pkgs.lib; };
in ...Every type is grounded in an MLTT type-checking kernel. The guard (check)
is derived from the kernel's decide procedure. The verifier (validate)
sends typeCheck effects through the freer monad for blame tracking. You
choose the error policy by choosing the handler.
fx.types.String fx.types.Int fx.types.Bool
fx.types.Float fx.types.Attrs fx.types.Path
fx.types.Function fx.types.Null fx.types.Unit fx.types.AnyEach wraps a builtins.is* check:
fx.types.String.check "hello" # true
fx.types.Int.check "hello" # falseBuild compound types from simpler ones:
# Record with typed fields (open — extra fields allowed)
PersonT = Record { name = String; age = Int; };
PersonT.check { name = "Alice"; age = 30; } # true
# Homogeneous list
(ListOf Int).check [ 1 2 3 ] # true
# Optional value
(Maybe String).check null # true
(Maybe String).check "hello" # true
# Tagged union (two branches)
(Either Int String).check { _tag = "Left"; value = 42; } # true
# Tagged union (open)
(Variant { circle = Float; rect = Attrs; }).check { _tag = "circle"; value = 5.0; } # trueListOf sends per-element typeCheck effects with indexed context
(List[Int][0], List[Int][1], ...) so handlers report exactly which
element failed. Record sends per-field effects (Record{age, name}.age)
and delegates to each field type's .validate, so nested Records and
ListOf fields decompose recursively. Variant delegates to the active
branch's .validate.
Narrow any type with a predicate (Freeman & Pfenning 1991; cf. Rondon et al. 2008):
Nat = refined "Nat" Int (x: x >= 0);
Port = refined "Port" Int (x: x >= 1 && x <= 65535);
NonEmpty = refined "NonEmptyString" String (s: builtins.stringLength s > 0);
# Predicate combinators
refined "Safe" String (allOf [ (s: s != "") (s: !(builtins.elem s blocked)) ])
refined "Either" Int (anyOf [ (x: x < 0) (x: x > 100) ])Built-in refinements: positive, nonNegative, inRange, nonEmpty, matching.
Types themselves have types, stratified to prevent accidental paradoxes
(universe levels are enforced by the kernel's checkTypeLevel; see Known limitations):
Type_0 # Type of value types (Int, String, ...)
Type_1 # Type of Type_0
Type_2 # Type of Type_1
# typeAt n works for any n; Type_0 through Type_4 are convenience aliases.
# 4 is arbitrary — for NixOS configuration you'll rarely need more than Type_1.
(typeAt 0).check Int # true — Int lives at universe 0
level Int # 0An effectful computation is a freer monad value: a tree of effects with
continuations. send creates an effect. bind sequences computations.
run interprets the tree through a handler.
# A computation that reads state, doubles it, writes it back
comp = bind get (s:
bind (put (s * 2)) (_:
pure s));
# Run with state handler
result = fx.run comp {
get = { param, state }: { resume = state; inherit state; };
put = { param, state }: { resume = null; state = param; };
} 21;
# result.value = 21, result.state = 42Write the validation once. Swap the handler to change error policy.
packed = ServiceConfig.pack config;
validation = ServiceConfig.validate packed;
# Strict — abort on first error
strict = fx.run validation {
typeCheck = { param, state }:
if param.type.check param.value
then { resume = true; inherit state; }
else { abort = null; state = state ++ [ param.context ]; };
} [];
# Collecting — gather all errors, continue checking
collecting = fx.run validation {
typeCheck = { param, state }:
if param.type.check param.value
then { resume = true; inherit state; }
else { resume = false; state = state ++ [ param.context ]; };
} [];The resume vs abort distinction: resume feeds a value back to the
continuation and keeps running. abort discards the continuation and
returns immediately. Handlers should return one of
{ resume = value; state = ...; } or { abort = value; state = ...; }.
If both are present, abort takes priority.
| Module | Operations | Purpose |
|---|---|---|
state |
get, put, modify, gets |
Mutable state |
error |
raise, raiseWith |
Error handling |
reader |
ask, asks, local |
Read-only environment |
writer |
tell, tellAll |
Append-only log |
acc |
emit, emitAll, collect |
Value accumulation |
choice |
choose, fail, guard |
Nondeterminism |
conditions |
signal, warn |
Common Lisp-style restarts |
typecheck |
sent by type.validate |
Type validation with blame |
linear |
acquire, consume, release |
Graded linear resource tracking |
Effectful lazy sequences. Each step yields Done (finished) or More
(element + continuation):
# Generate, transform, consume
result = fx.run
(fold (a: b: a + b) 0 (take 5 (map (x: x * x) (range 1 100))))
{} null;
# result.value = 55 (1² + 2² + 3² + 4² + 5²)Available: fromList, iterate, range, replicate, map, filter,
scanl, take, takeWhile, drop, fold, toList, length, sum,
any, all, concat, interleave, zip, zipWith.
The fx attrset is the entire public API:
fx.pure fx.impure fx.isPure fx.match
fx.send fx.bind fx.map fx.seq
fx.pipe fx.kleisli
fx.run fx.handle fx.adapt fx.adaptHandlers
fx.types.mkType fx.types.check fx.types.validate
fx.types.make fx.types.refine
fx.types.String fx.types.Int fx.types.Bool fx.types.Float
fx.types.Attrs fx.types.Path fx.types.Function fx.types.Null
fx.types.Unit fx.types.Any
fx.types.Record fx.types.ListOf fx.types.Maybe
fx.types.Either fx.types.Variant
fx.types.Pi fx.types.Sigma fx.types.Certified
fx.types.Vector fx.types.DepRecord
fx.types.Linear fx.types.Affine fx.types.Graded
fx.types.refined fx.types.allOf fx.types.anyOf fx.types.negate
fx.types.positive fx.types.nonNegative fx.types.inRange
fx.types.nonEmpty fx.types.matching
fx.types.typeAt fx.types.level
fx.types.Type_0 .. fx.types.Type_4 # convenience aliases; typeAt n works for any n
fx.effects.get fx.effects.put fx.effects.modify fx.effects.gets
fx.effects.state fx.effects.error fx.effects.typecheck
fx.effects.conditions fx.effects.reader fx.effects.writer
fx.effects.acc fx.effects.choice
fx.effects.linear
fx.stream.done fx.stream.more fx.stream.fromList
fx.stream.iterate fx.stream.range fx.stream.replicate
fx.stream.map fx.stream.filter fx.stream.scanl
fx.stream.take fx.stream.takeWhile fx.stream.drop
fx.stream.fold fx.stream.toList fx.stream.length
fx.stream.sum fx.stream.any fx.stream.all
fx.stream.concat fx.stream.interleave fx.stream.zip fx.stream.zipWith
fx.types.hoas fx.types.verified
fx.types.elaborateType fx.types.elaborateValue
fx.types.extract fx.types.verifyAndExtract
fx.types.decide fx.types.decideType
fx.kernel.pure fx.kernel.send fx.kernel.bind
fx.kernel.pipe fx.kernel.kleisli
fx.trampoline.handle
Types additionally expose:
T.check v -- decide via kernel (elaborate + type-check)
T.prove term -- verify a HOAS proof term against the kernel type
T._kernel -- the kernel type (HOAS tree)
Computations are freer monad values: Pure value or Impure effect continuation,
constructed via comp.pure and comp.impure (the comp module is the single
source of truth for the Computation ADT). bind appends to an FTCQueue
(catenable queue) in O(1). send uses an Identity queue sentinel so the
trampoline can skip the identity continuation application entirely.
The interpreter uses builtins.genericClosure — Nix's only iterative
primitive — as a trampoline, giving O(1) stack depth for the main
dispatch loop. Each step calls the handler for the current effect, processes
the continuation queue inline via recursive applyQueue, and produces the
next computation node — one genericClosure step per effect.
deepSeq on the handler state in the key field breaks thunk chains
that would otherwise blow memory. Test suite validates 100,000 operations;
manual runs confirm 1,000,000 operations in ~3 seconds with constant memory.
Certified carries a boolean witness, not an inhabitation proof.
Certified(A, P) = Σ(v:A).{p : Bool | p ∧ P(v)} stores the boolean
result of P(v) as its second component rather than a term inhabiting
P(v). Predicate evaluation happens at construction time and produces
no transportable proof term. For genuinely propositional content, use
Pi with identity types and the J-derived combinators (sym,
trans, cong, transport) from fx.types.hoas.
Universe levels are partially enforced. For kernel-backed types,
checkTypeLevel computes the correct universe level from the typing derivation.
For non-kernel types, the universe field remains a trusted declaration
— nothing prevents a user from declaring universe = 0 on a type that
operates at a higher level. Computing sup_{a:A} level(B(a)) for
arbitrary type families requires evaluating on all domain values, which
is undecidable. The hierarchy prevents accidental paradoxes; the kernel
enforces it for types it knows about.
Effects are string-keyed, not extensible. Kiselyov & Ishii (2015)
contributes both the freer monad encoding with FTCQueue and extensible effects
via open unions. nix-effects implements the first but not the second. Effect
handlers go into a single flat attrset per run call; name collisions are
silently accepted (last handler wins via attrset merge).
O(1) stack depth caveat. The trampoline gives O(1) stack for the main
dispatch loop. Continuation queue application is inlined as a recursive
function (depth-limited to 500) with a genericClosure fallback for deep
pure chains, so chains of 10,000+ pure binds are handled iteratively.
Queue rotation (viewlGo) uses genericClosure for deep left-nested
trees. The remaining stack risk is in user-supplied handler functions
that recurse deeply within a single trampoline step.
Handler state must be deepSeq-safe. The trampoline uses
builtins.deepSeq on handler state at each step to break thunk chains.
This means handler state must not contain functions (closures), since
deepSeq on a function is a no-op in Nix -- thunks captured inside
closures survive the eager evaluation and can accumulate. All built-in
handlers use scalar or flat-attrset state (safe). Custom handlers with
closure-valued state may lose the thunk-breaking guarantee.
# Run all tests via nix-unit (flake)
nix flake check
# Run all tests via nix-unit (non-flake)
nix-unit ./tests.nix
# Evaluate test results directly
nix eval --impure --expr \
'let fx = import ./. { lib = (builtins.getFlake "nixpkgs").lib; };
in fx.tests.allPass'
# => trueTests cover algebraic laws (functor, monad), all type constructors including dependent and linear types, the trampoline at 100k operations, error paths, streams, and HOAS proof verification.
Key papers that shaped the design:
-
Martin-Löf (1984) Intuitionistic Type Theory. Pi, Sigma, universe hierarchy. nix-effects implements these in an MLTT type-checking kernel (
src/tc/) — all types are grounded in the kernel, which operates atnix evaltime. -
Findler & Felleisen (2002) Contracts for Higher-Order Functions. The guard/verifier decomposition follows their strategy: first-order types check immediately, higher-order types (Pi) defer to elimination.
-
Freeman & Pfenning (1991) Refinement Types for ML. The concept of narrowing a type with a predicate. nix-effects'
refinedconstructor and predicate combinators implement runtime refinement checking. Rondon, Kawaguchi & Jhala (2008) extended this with SMT-based inference (Liquid Types); nix-effects uses predicates rather than SMT solvers. -
Plotkin & Pretnar (2009) Handlers of Algebraic Effects. The handler pattern.
resumeinvokes the continuation,abortdiscards it. -
Kiselyov & Ishii (2015) Freer Monads, More Extensible Effects. The freer monad encoding and
FTCQueue(catenable queue) that give O(1) bind and make effectful validation practical at scale. nix-effects uses the freer encoding and FTCQueue but does not implement the paper's extensible effects (open unions, Member constraint). -
Orchard, Liepelt & Eades (2019) Quantitative Program Reasoning with Graded Modal Types. The graded linear type model. nix-effects'
Linear,Affine, andGradedtypes implement resource-usage tracking following this quantitative framework.
nfx by Victor Borja (Apache-2.0) shaped the API
design of this project. The adapt handler combinator, the mk { doc, value, tests } structured module pattern, and the effect module vocabulary (state,
acc, conditions, choice, streams) all come from nfx. nix-effects builds a
different core on freer monads with FTCQueue (Kiselyov & Ishii 2015) and adds a
type-checking kernel and dependent type system that nfx does not attempt, but
the overall API owes a clear debt to that project.