Zain Dana Harper Map

Elements Swatches Studies Site index

BuildLang BLDLNG

A function's type lists what it may touch. The compiler checks it, proves your laws and builds native code through C.

BuildLang is a systems programming language in which a program declares what it is allowed to touch. The compiler checks those declarations and its memory rules, then emits native code through C. It ships with a CLI, editor support, two-way C integration and experimental shader output.

cargo install buildlang --version 1.15.0 --locked

Release 1.15.0, 14 November 2026. Each figure below opens to the pull request it was read from, and names the release that first carried that work, or says it is on main after this release or still in review.

The registry

First released in 1.11.0 (#137); first released in 1.12.0 (#156, #160).

Our own tools, rewritten in BuildLang and checked byte for byte against the originals they replace.

buildc pkg build

sha256, from Flywheel: Published with the package manager in 1.11.0, pure BuildLang.

  • from Flywheel
  • from build-color
  • from this site's tools
  • the standard library
  • from Low Water, AGPL-3.0-only

The index, with a SHA-256 for every version: registry/index.json.

Laws and contracts

First released in 1.12.0 (#138).

A law is a property you state beside the code, such as a function never returning less than its input. The compiler proves it, refutes it with a counterexample, or says why it cannot tell; it does not test by sampling alone.

buildc verify laws.bld

The whole account: docs/VERIFY.md on main.

Translation validation

First released in 1.12.0 (#161, #162).

Translation validation means proving, function by function, that the C we emit does what its source says: the same traps, the same results. It checks each compiled program, not the compiler for every program.

buildc tv program.bld

Parallel by default

First released in 1.11.0 (#136).

par_for and par_map run on every core, and the checker proves from the source that the body is safe, so the result matches the serial loop byte for byte.

The parallel call is written out: BuildLang checks its safety, and does not find parallelism on its own.

BUILD_PAR_THREADS=8 buildc run program.bld

The whole account: docs/PARALLEL.md on main.

Into C, and out of it

First released in 1.11.0 (#135).

Low Water's rules are written in BuildLang and linked into raw-native's C++ host through a plain C header.

  • 16 of 16 checks of raw-native's own C++ test pass against the BuildLang library, as they do against the C++ module

    A planted threshold fails 1. The story expression language is not ported: a record that needs it makes lw_rules_create refuse it with an error naming the record. buildlang #158, merged 9 November 2026 (3c7cc54), first released in 1.12.0.

  • 12 of 12 DETMATH goldens hold (DETMATH: BuildLang's deterministic maths, the same bits on every machine, with fast-math shortcuts off), and 40 of 40 combat traces match the game's own corpus

    The moves file builds to 168,234 bytes, identical to the golden. Both planted trace faults are caught. buildlang #158, merged 9 November 2026 (3c7cc54), first released in 1.12.0.

  • 34 of 34 held-out tasks pass in each of two samples, Wilson 95% 0.90 to 1.00

    The tasks were sealed before any generator saw them. Both samples are two draws of one model with one prompt, and the task writer also wrote the compiler changes, so the tasks may sit closer to the docs than an outside writer's would. buildlang #158, merged 9 November 2026 (3c7cc54), first released in 1.12.0.

The whole account: docs/LANGUAGE-COMPLETE.md on main.

BuildDB moves in

First released in 1.11.0 (#118, #119).

BuildDB is the database written in BuildLang. The compiler already writes a program into it as tables you can query; the database itself is moving into the language's repository.

The move is not on GitHub yet, so nothing here links to it.

buildc bql query prog.bld "SELECT DISTINCT function FROM effects WHERE effect = 'Network'"

The first step

Choose what the function may touch and watch it build or fail.

With scripts on, this is a function you can change: choose what it declares and see whether it builds.

The function above follows BuildLang's rule in the page itself: read_file needs FileSystem, println! needs Console, and effects join with +. The messages copy the wording of the captured run below. The rule is written down in docs/EFFECTS_GUIDE.md.

Captured from buildc check

fn load_config() {
    read_file("ops.toml");   // reaches the filesystem
}

$ buildc check missing_effect.bld
function `load_config` performs effect `FileSystem` but does not declare it
help: add ~ FileSystem to the signature

fn load_config() ~ FileSystem { read_file("ops.toml"); }

$ buildc check load_config.bld --receipt receipt.json
Type checking... OK

The language guide goes on from here: the getting-started guide, the source.

Verified 14 November 2026: the release and its date from GitHub, and crates.io lists 1.15.0; the merge state of every linked pull request from GitHub on the same day; each figure read from the body of the pull request it links.