43 decisions
Why Diaspar is the way it is
Every choice in the language is a record: what was decided, the reasons, and what was turned down. Here they are, by topic.
The records are the language's own, as they stood on 2026-11-18, written for the people who build Diaspar. Their code is a sketch of a design, and an older record may show syntax that a later one changed; the programs that run are in the tour. Open source soon. Diaspar is in development, and its source is not public yet.
The language as a whole
What Diaspar is, and what it takes from the Lisps before it.
- D001Diaspar is a standalone general-purpose languageaccepted
- D002No separate low-level dialectgoal accepted; mechanism proposed
- D003A compiled language with a live REPLaccepted; C backend proposed
- D009Core vocabulary follows Clojureaccepted
- D013Core value semantics: equality, numbers, strings, sequences, the REPLaccepted
Syntax
Brackets, the dot, labels, operators.
- D008Brackets work as in Racket: interchangeable, shape preservedaccepted; data literals proposed
- D029One dot for members: modules, types, fieldsaccepted; details proposed
- D030Named arguments with labels
name:accepted; details proposed - D022Operators are protocol methods; strings concatenate with
+and interpolateaccepted
Data and patterns
Records, enums, protocols, one pattern language, numbers, sequences.
- D010Data and polymorphism: records, opaque types, protocolsaccepted in part; the rest proposed
- D015One pattern language for the whole language; hygienic macros as in Racketaccepted
- D040Sequence patterns match the end of a sequence;
&staysaccepted; not implemented - D036Ranges, slices, iterators and generatorsaccepted
- D038Decimal numbersaccepted
- D043Two printed forms of a value,
ShowandDisplay; BigInt in the core, a number with the literal12bigaccepted; not implemented - D034Refinements from the audit of the standard libraryaccepted
Effects, errors, state
One mechanism for errors, resources and whatever a function asks of its caller.
Concurrency
Tasks without colored functions.
Types and memory
Inferred types that warn; reference counting that reuses memory.
Modules and packages
Names, imports, packages, data read when a program is compiled.
The live environment
The REPL's debugger, and changing a program that is running.
The tools
Diagnostics, tests, the formatter, documentation, one command for all of it.
- D014Diagnostics show the code, with notes and hintsaccepted as a goal; format proposed
- D019Terminal output is colored and carefully designedaccepted as a goal; details proposed
- D016Tests and benchmarks are part of the language from the startaccepted
- D031The formatter:
diaspar fmtaccepted; details proposed - D037Tooling: one
diasparcommand, tasks as programs, scripts, the toolchainaccepted - D039Tools for agents and people: diagnostics that name the fix, introspection, quiet outputaccepted in part
- D041Documentation is generated from doc strings and checked as code isaccepted; not implemented
The standard library
Modules whose design was a decision.
The implementation
The compiler, the runtime, calling C, the browser.
- D012The phase-0 bootstrap interpreter is written in Rustsuperseded
- D026The runtime and the C backend for stage Baccepted
- D021Calling C (FFI) is built in, in the Diaspar implementationaccepted; the details in design/ffi.md (2026-11-18, by delegation)
- D032Repository layout and file sizeaccepted
- D042The browser's build: the whole
diasparas 64-bit WebAssembly; no 32-bit targetsaccepted; a spike built