The description and the program are the same artefact.
Two developers sit at one screen. One is walking the other through a function he just wrote, pointing at the code with his finger as he goes. He does not read every symbol. He summarises: this checks whether the number divides evenly, then loops from one to fifteen and prints fizzbuzz on the right multiples. He is describing the program, not reading it, because the text on the screen and the sentence in his mouth are two different things.
That gap, between what a person says a program does and what is actually written there, is the whole problem code review lives inside. Humans do not speak in brackets and semicolons. We speak, and think, in sentences.
Here is the turn: in Voxlang, the sentence he would say out loud is what the program already looks like. There is no translation step, because the description and the program are the same artefact.
Two consequences follow, stated plainly. Anyone can read a Voxlang program and follow what it does, including someone who has never written a line of any language, so review stops being gatekept by who knows the syntax. And in 2026, more and more code is written by models, and somebody accountable still has to sign it off. A source that skim-reads like prose lets that person read a whole program the way they read a novel: follow what it does, and notice the paragraph that does not belong. Voxlang makes machine-written code auditable by the human who answers for it.
This is a property of the syntax, not a proof of correctness: reading clearly and running correctly are different things, and Voxlang only promises the first.
To check whether one number divides another evenly, see if the remainder is zero. Then, for every number from one to fifteen, print it. But if it divides evenly by six, print fizzbuzz. If it divides evenly by two, print fizz. If it divides evenly by three, print buzz.
To 'check divisibility' with a number called x and a number called y. Return a boolean, x modulo y is 0. For each number from 1 to 15, print the number, but if 'check divisibility' of the number and 6 is true print "fizzbuzz", but if 'check divisibility' of the number and 2 is true print "fizz", but if 'check divisibility' of the number and 3 is true print "buzz".
Memory, without a garbage collector.
Voxlang makes a promise about memory too, and keeps it without a garbage collector, without a runtime, and without tracing anything while the program runs. The guarantees come from compile-time structure and from small inline checks the compiler writes directly into the generated assembly.
A Voxlang program never touches a raw pointer directly. The compiler allows one explicit escape hatch, casting a buffer, text or list as a number, which hands back the pointer value itself for the program to use as an ordinary number. Outside that cast, every access to memory goes through a buffer the compiler manages: it owns the allocation, tracks the size, and knows the lifetime. A dynamic buffer grows as you append to it, its size tracked explicitly. A fixed buffer does not grow: a write past its declared capacity is refused rather than reallocated, so a bound you wrote down stays a bound.
An out-of-bounds access is not a crash. It becomes a no-op, an error flag is set, and execution continues, so the program can check that flag and handle it itself, with no traps, no exceptions, no runtime handler catching anything on its behalf. Buffers, file descriptors, and other resources are tracked the same way, and released deterministically on exit even when the cleanup was never written by hand.
None of this is Rust wearing a different syntax, and the project says so itself. As the compiler's own README puts it: "While Vox does not replicate Rust's type system, it aims for a similar practical outcome: predictable, memory-safe programs without a garbage collector or runtime system." It is its own method, judged by its own results, not a claim to be something else.
Source: README.md, Memory Safety Model
Small binaries, nothing in the way, assembly you can read.
Voxlang compiles straight to assembly with no runtime system and no standard library, so its binaries are small by construction, well suited to static utilities and constrained environments. Built today with vox 0.4.9: the compiler's own hello.vox compiles to a static 6,688-byte executable, and the clock example on this page compiles to 11,128 bytes. Neither links libc.
That smallness is honest about what it buys. There is no interpreter to start and no garbage collector to pause the program mid-run: the binary is the program, making the system calls it makes and nothing else. Voxlang does not claim to be faster than C; matching C's performance on numeric benchmarks is a stated goal, not a result yet.
What the compiler emits is plain NASM, readable the same way the source is. The runtime it depends on is a directory of assembly macros, coreasm: on the Fedora Copr package it sits as a plain directory beside the compiler binary, and from cargo install it is embedded in the binary itself and unpacked to a cache directory the first time it runs. Either way it ends up as real files on disk, yours to read, and on your own copy, to change.