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.

Open source

Faber's source is open. The compiler front end, the reference runner, the standard library (Norma), the grammar, the locale packs and the corpus are in faberlang/faber under MIT OR Apache-2.0. The repository builds a working faber that checks, formats and runs programs.

Faber is experimental through version 1. The language changes constantly, and breaking changes ship in minor releases. Pin an exact version and read the release notes before you upgrade.

What is open#

ComponentWhat it is
Compiler front end and middleLexer, parser, semantic analysis, the typed intermediate representations (HIR and MIR) and the checks that run on them
The MIR runnerExecutes Faber programs directly; the reference every other target is checked against
C and Cranelift code generatorsReadable C and native objects through Cranelift. Both are previews that cover a growing subset of the language and reject the rest by name
Artifact formatsFHIR and FMIR: serialized analyzed HIR and MIR images that faber can load and run
The `faber` commandcheck, run, test, build, format, convert, corpus and targets
NormaThe standard library: files, processes, time, text, JSON, TOML, HTTP and more
Grammar and locale packsThe grammar and the reader-locale packs
CorpusSeveral hundred small programs with expected output, and the suites that run them
Agent skillsTwo guides for coding agents: writing Faber, and changing the repository
DocumentationThis site, its Markdown sources, and the generator that renders it

What is not in the public source#

The official faber release also carries code generators that are not part of the public source: Rust, Go, TypeScript, Swift, Python, Haskell, LLVM, WebAssembly and the GPU emitters. Installing a release, not building the public tree, is the way to get every target. See the target matrix for what each target covers.

Public repositories#

Everything below lives under the faberlang organisation. Each repository's README states its own status and licence.

RepositoryDescription
faberThe open-source core: compiler front end, runner, standard library, grammar
releasesTagged CLI release assets and prebuilt archives
trigaGraphics and geometry library
gradusAutograd and ML library: gradients, loss, optimizers, NN primitives, training
telaUI and view library
tree-sitter-faberTree-sitter grammar and editor packaging for syntax highlighting
faberlang.devThis website

Three archived repositories are kept for history: faber-1.x held Faber 1.0 to 1.12 (its version tags were carried into faber, so a project pinned to a 1.x tag keeps resolving), and norma and hosts are superseded. The standard library now lives in faber under lib/norma.

Reporting issues#

GitHub Issues is the fastest way to reach the project. The repositories do not take outside pull requests.

ProblemWhere to report
Compiler or CLI behaviour (bugs, diagnostics, crashes)faberlang/faber · Issues
Standard libraryfaberlang/faber · Issues
Documentation or website problemsfaberlang/faberlang.dev · Issues
A library or toolThe matching repository above

Include the faber version and a minimal reproducing package.

Maintainer#

Faber is designed and maintained by Ian Zepp.

For anything reproducible — a bug, a broken page, a package that will not build — an issue on the owning repository will get a faster and more useful answer than email, because it lands next to the code and stays searchable for whoever hits it next.