Roadmap
What Nish has built and what is left, with one page per work package. A
checked box is built and on main; an unchecked one is not. An item marked
(open question) waits on a decision that has not been made, and one marked
(deferred) is wanted but not scheduled. Each package's design and its
reasons are in its design note on GitHub, linked from its page; the state is
kept here, and a pull request that lands a stage ticks its box.
Milestones
- M1, programs: fib, gcd and a string CLI build with
nish --link, under 20 KB - M2, data: nbody with structs and arrays matches C's output bit for bit
- M3, Rust parity: the benchmark table within 10% of Rust, wasm and N-API demos
- M5, self-hosting:
src/compilessrc/, and stage3 is byte-identical to stage2 - M6, one compiler: stage0 deleted rather than frozen, first released in 0.7.0
- M4, 1.0: a frozen language reference (open question). Nish stays on 0.x, and a breaking change moves the minor, until 1.0
Up next
In order. Each package's page says what its next stage is and where it is specified.
- WP49:
async/awaiton the server, and the TechEmpower top: meet stage 6's gate. - WP39: The HTTP server: a TechEmpower entry, then a general-purpose server: G7's one handler, the
nish/net/http-serverfaçade. - WP43: The HTTP application layer: stage 3, static files.
- WP21: Packages: S4, the build cache.
Open questions
- M4: when to declare 1.0.
- WP22: Arrow functions as the declaration form: whether stage D rejects a
functiondefinition. - WP57: Module-scoped names: whether two exported functions of one package may share a name, and what that does to the C surface (S2).
- WP59: The wasm arena in a second, unexported memory: how module storage crosses into the hidden memory, how a page that must run in Safari gets a single-memory module, and how large the exchange area is under
--memory(S3). - WP60: Dynamic dispatch over interfaces: whether to build
Dyn<I>; the design note measures it against the hand-written dispatch and recommends shipping interface method signatures (stage 1) now, withDyn<I>in registers and in stored places each gated on its own build's timing. - WP61: Typed JSON, constraints and coercion in one pass: the shape of the
constraintsoption, whether to record which keyword failed, whether encode checks constraints in a-gbuild, and whether a coerce class may reach a strict one. - WP62: Nish classes from a JSON Schema: whether its typed JSON prerequisites land as its S1 or in WP61, a reverse generator,
readOnly/writeOnly, unknown andx-*keywords, nullablebooleanand type-discriminated unions, presence flags, field-name style, where the generator lives, and whetherformatis checked by default (S5). - WP64: Temporal: how option bags such as
{ largestUnit: "year" }get a layout, whether the time zone database is embedded by default,Duration's field width,epochNanosecondswithoutbigint, and whether aRangeErrorstays a panic. - WP65: The surface a lexer port asked for: whether to build
toString()on a number, which LANGUAGE.md refuses today, or keep the rule and make the refusal name the template literal. - WP66: C libraries from their headers: what C may do with a callback (S6), and the owner's decisions D1 to D7: the subcommand's name, where it lives, files per target,
i8andi16, the opaque class's spelling, what linking may run, and whetherstd/sqliteis regenerated. - WP39: The HTTP server: a TechEmpower entry, then a general-purpose server and WP49:
async/awaiton the server, and the TechEmpower top: whether and when to submit to TechEmpower. - WP54:
asyncon wasm, with the page as the executor: whether to build it, which waits on a program that must run on a Worker, and its other questions.
In progress and proposed
Landed
Not built
- WP41, a 64×64→128 multiply: measured on Poly1305, 14% to 21% faster natively but 19% to 27% slower on wasm32, so it was declined.
- WP48's first design, a whole-program 32-bit mode or an
i32pool: measured and declined on 2026-11-11; ports use a tree's first-child and next-sibling links instead, which took about half the memory. WP48 is reopened above for linked classes the compiler picks.
WP-P, the pipeline prep, landed without a note, and WP11, documentation, is folded into every package.

