Reference
The reference is for readers who already know the basics — if you have not yet, the Learn track is the front door. Reference pages are short, dense, and assume the rest of the language is already familiar.
The reference has four sections.
Language reference
The grammar, types, operators, and built-in primitives, exactly as the implementation accepts them.
- Lexical structure
- Operators and precedence
- Type system
- Functions
- Tensors
- Loop primitives
- Pattern matching
- Intrinsics
- Grammar (EBNF)
Compiler internals
The shape of the implementation: the stages, what each one does, and where you would look in the source tree.
- Pipeline overview
- Lexer · Parser · Type checker
- CEIR · MIR · x86 backend
- ELF and linking
- Diagnostics
Specification
The semi-formal description of what the language means. Implementation-independent in intent; written in service of a future second implementation.
Planned features
Features in the spec or the roadmap that are not yet fully
implemented. Each page describes the design intent, what (if
anything) has already shipped, and where it sits on the
roadmap. A few of these pages — @io effects
and string literals — describe machinery that has already landed
in part; they remain here because their full surface is still
ahead.