This roadmap shows priorities and readiness, not promised dates. A feature listed here is not part of the current language or a public release until its documentation says so.
Now
- Maintain the released v5.6 grammar, standard library, runtime, and tools as one coherent product line.
- Continue expanding the common execution surface across the interpreter, Rust, and Python.
- Exercise files, packages, diagnostics, and standard-library APIs in real applications.
- Keep WASM, the playground, web targets, and package tools on the same version.
Next
- Align installer, download, package, and documentation versions before publication.
- Add practical APIs around numbers, strings, collections, structured data, and network boundaries.
- Improve package creation, locking, vendoring, and offline builds.
- Make diagnostics, formatting, and language-server support fit everyday editing better.
Later
- Introduce clear compatibility boundaries before adding more backends or independent implementations.
- Expand debugging, profiling, artifact-size, and performance tools for users.
- Develop general recursion, portable values, state cells, trampolines, deterministic printing, and error handling needed to implement the Lispex interpreter in Topaz.
Research
- Expand differential and fuzzing tools that find places where code generators misunderstand the language.
- Consider model checking or mechanized proofs only where there is a concrete artifact and a useful way to reproduce the result.
- Keep async syntax, recoverable faults, grapheme APIs, and user-defined templates as research topics until a future language decision accepts them.