LIT is the Lispex interpreter used as a bounded dogfood and integration artifact. It is written in Topaz, and one canonical source lineage is exercised through direct execution, generated Rust, generated Python, and Web routes. This demanding program can expose defects in checking, lowering, runtime behavior, and host boundaries.
Choose the right path
- To ship a Topaz application, choose one of the supported Topaz output targets.
- To understand LIT, read it as evidence that a substantial Lispex program exercises several parts of the Topaz toolchain together.
- To use Lispex as a product, follow the Lispex product documentation. This page describes only the boundary observed from Topaz.
What the evidence means
A passing LIT check means the named program behaved as expected on the named routes and within the capabilities selected by that check. Unsupported capabilities fail explicitly. Because all four routes come from one source lineage, their agreement is useful regression evidence, not evidence from four independent implementations and not proof that the two languages are equivalent.
Product boundary
LIT is not included in a Topaz installation. It is not a Topaz backend or
output target, and there is no --target lit product path. It does not add
Lispex syntax, primitives, packages, an ABI, or runtime guarantees to Topaz.
Its checks are used when a related compiler or host boundary needs that
evidence; they do not turn every Lispex program into a supported Topaz
application.