Renderingen-US

Experimental through version 1. Version 0 was alpha. This is the first language release: the interface is relatively stable, not frozen. Nothing is promised stable until version 2.

Toolchain

One binary does everything: faber. It bundles the Radix compiler, the Cista package resolver, a formatter, a test runner, and an in-process interpreter. There is no separate build tool to install.

The commands you will actually use#

faber init my-app          # create a package
faber check my-app/        # typecheck, no output written
faber run my-app/          # run in-process on clif-jit; --device reference for the MIR runner
faber build my-app/ -t rust  # compile to a target
faber test my-app/         # run inline test suites
faber format my-app/       # report files that would change (--write applies)
faber explain return        # what does this keyword do?

check is the one you run constantly — it is the full frontend (parse, resolve, typecheck) with nothing written to disk.

Everything faber exposes#

CommandDoes
initcreate a new package
checksemantic analysis on a file or package
buildcompile and write output for a target
runrun a single file, package, or archive in this process; with --target, pick the engine
replinteractive MIR runner, re-lowering each line
testrun +++ faber test sections and test cases on the runner, no Cargo or rustc
formatreport (or --write) canonical formatting at the source's own locale
convertconvert source between reader-locale surfaces (--to <locale>)
explainexplain a glyph, keyword, or grammar term
targetslist targets and their current capability notes
verifyaspect verification on a single file
emit, debug lex, debug parse, debug hir, debug mircompiler-phase inspection (debug is hidden; the bare phase names are hidden aliases for 1.19)

faber is for packages. radix is the developer tool for single files and compiler-phase inspection — see Inside Radix.

Run, or build#

CommandWhat happensWhen
faber runparse → typecheck → MIR, then compiles in memory with Cranelift and runs in-process; --device reference runs the MIR itself, --target builds for a target firstiterating, scripting, tests
faber build -t <target>lowers to the chosen target and writes the outputshipping, benchmarking

Both run the same frontend, so run typechecks exactly as strictly as build. run writes nothing to disk and needs no linker.

Where the rest lives#

PageWhat it covers
The faber CLIevery command in depth, plus scripting and the REPL
Compiling and targetsthe HIR/MIR/AIR lanes and what each backend supports
Target matrixgenerated: every corpus term × every backend
Packages with Cistafaber.toml, lockfiles, the package store
Inside Radixcompiler architecture, for people changing it