Topaz v5.7.0 is the current public release. The public command-line tools, runtime, npm installer, WASM compiler, documentation, and playground use the canonical topaz-5.7 language mode.
Topaz 5.7.0 includes contiguous mutable ByteBuffer, the Web allocation/return-memory repair, and the checked Web Application Loop. These are product capabilities on the existing topaz-5.7 language mode, not a separate language version.
Available components
- Native CLI for checking, running, emitting, and building programs
- Rust output for standalone native binaries
- Python output with its required runtime support file
- Raw WASM and web-worker output for browser applications
- Checked web-app scaffolding, loopback development, and complete managed static bundles
- Package commands and the browser playground
Recommended workflow
Install Topaz with the public installer or npm package, start with topaz check, establish behavior with topaz run, then build only the target you plan to deploy. Use topaz version --verbose when reporting an installation problem.
Current support
The interpreter, Rust output, and Python output cover the current grammar and standard-library families documented on this site. Browser builds support raw WASM, worker packages, and checked Web Applications that run from their generated static bundle. File, process, network, clock, and browser APIs remain tied to the host environment described on their individual pages.
Repository integration artifact
Lispex-in-Topaz has internal, bounded integration evidence for one measured source family, but it is not a released Topaz component or a public backend.
| Area | Current bounded status |
|---|---|
| Canonical source | One LIT source across the interpreter, generated Rust, generated Python, and Web routes |
| Primitive capability floor | 84 of 205 rows supported, consisting of 31 deterministic delegations and 53 machine implementations; 121 fail loudly |
| Guest-calling primitives | 6 of 18 supported through the common machine dispatcher; the rest fail loudly |
| Four-host evidence | Internal evidence covers a bounded check surface across all four routes |
| Lispex release observation | One installed LIT route participates in the 144-case joint receipt; Rust/LIT agrees on 65 cases and diverges on 79 |
| Provenance boundary | All four Topaz routes are variants of one LIT source; they are not independent implementations and no source-independence is claimed |
This artifact does not add syntax, standard-library guarantees, installer contents, or a new public backend.
Known limits
Compression helpers are currently available on the Rust-backed library path but are not portable to every output target. Concurrent task ordering is intentionally unspecified. Some future language ideas listed on the roadmap are not accepted syntax yet. The Lispex integration remains bounded to 84 of 205 primitive rows, its exact four-host check surface, and the 144-case joint receipt. It does not establish whole-language equivalence.
Command reference
topaz version --verbose