Skip to content

Capabilities and boundaries ​

YL combines a grammar, authored static analysis, editor metadata, and host hook contracts in a reusable language artifact. The examples demonstrate deliberately small languages; Mini TypeScript is not an implementation of the TypeScript standard.

AreaAvailable nowBoundary
SyntaxSpanned ASTs, modules, imports/exports, concrete/abstract nodes, patterns, pipes, precedence, trivia, syntax checksNo generated target-language parser or incremental parsing
ReferencesAuthored lexical scopes, declaration identity, shadowing, duplicates, ordered visibility, hoisted registration through explicit precedenceTarget-language import/export resolution is not supplied automatically
TypesLanguage-owned symbols, union contributions, restrictions, operator rules, isolated per-call inferenceNo flow-sensitive literal types or branch narrowing
Compound typesStructural interfaces, tuples, homogeneous/mixed lists, explicit type parameters, recursive structural comparisonNo complete TypeScript compatibility, recursive named-type solver, or prototype system
DiagnosticsTerminal/JSON diagnostics, grouped source annotations, optional origin tracingOrigin tracking is an authored policy, not automatic history for every type
HostsReusable Rust API, unevaluated hook dispatch, interpreter/JavaScript/Wasm examplesExample hosts support an integer subset, not execution of all Mini TypeScript features
EditorYL formatting, declaration hover, generated examples, project-selected program diagnostics and highlightingNo completion, navigation/rename, or target-language formatter

Experimental contracts ​

The language and its Rust API are usable from checked-in examples. .ylc is a validated, versioned executable artifact; long-term format compatibility and a stable foreign-function ABI are not promised. Host hooks leave runtime values, control flow, and emitted code to the consumer.

Read the artifact contract and backend interface when embedding. The roadmap distinguishes future flow analysis, heuristics, ownership, and additional integration work from current features.

Declarative languages. Reusable tools.