Topazdocs
Project

Roadmap

Product priorities from the unified Topaz 5.7.0 release toward the next public 5.8.0 minor.

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

  • Topaz 5.7.0 with language mode topaz-5.7 is the current public product.
  • Compiler, runtime, npm installer, artifacts, documentation, and Playground identify the same 5.7 line.
  • Fixed-length mutable ByteBuffer removes the boxed-byte assembly bottleneck while immutable Bytes and the existing native, Python, raw Web, and Web Worker contracts remain compatible.
  • The installed Web Application Loop can scaffold, check, test, serve, package, and run a typed browser application from a complete managed static bundle; Data Lens and Markdown Live exercise that path offline.
  • Run targeted differential checks when a related implementation changes. Reserve full cross-platform and full differential campaigns for the public-minor RC that owns them.

Next

  • Continue dogfooding the installed browser path and repair only concrete blockers reproduced by maintained applications.
  • Decide explicit HTTP service and local persistence or network capability boundaries from real application demand.
  • Improve package distribution, editor integration, debugging, profiling, artifact-size reporting, and performance tools where they change a user decision.
  • Consider language ergonomics only when libraries, diagnostics, or tooling cannot solve a maintained application problem cleanly.

Release sequence

  1. v5.7.0 (current) unifies compiler, runtime, language mode, packages, artifacts, npm, WASM, Playground, documentation, and maintained Web applications on the 5.7 line.
  2. Nonzero 5.7 patch checkpoints remain internal development milestones with production-quality validation but no public deployment.
  3. v5.8.0 is the next normal public minor and will publish only after its accumulated product work and user-visible version surfaces can move together.

Later

  • Keep broad framework, ambient host authority, and new syntax outside a product slice until a concrete maintained application requires them.
  • Preserve explicit older language modes as compatibility inputs rather than parallel current identities.

Bounded integration evidence

LIT and Lispex integration records remain useful internal compatibility and regression evidence. They do not define this release queue, make LIT a public Topaz backend, or establish whole-language equivalence. Large LIT, N-way, mutation, and differential campaigns run only when their owned semantics change or an applicable release candidate requires them.

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.

Continue reading