Specification
Language contracts define syntax and behavior; backend support varies by source shape. Check implementation status for route limits and the linked fixtures for tested cases.
How to read these docs
The specification states language rules and implementation boundaries. The learn guides teach workflows; the cookbook collects copy-paste patterns with links to their full contracts.
Language
| Topic | Contract |
| Units | Files, imports, modules, and entry points |
| Syntax | Source forms and grammar |
| Values | Literals, containers, equality, and value operations |
| Types | Type forms, inference, refinements, and proofs |
| Dependent types and indexed data | Refinements, Pi and Sigma types, GADTs, first-class Type values, type-level functions, and runtime indices |
| Kernel, erasure, and soundness | Trusted core rules, the erasure and ABI model, and the soundness risk register |
| Functions | Calls, parameters, closures, and function contracts |
| Control flow | Branches, loops, exits, cleanup, and error handling |
| Operators | Precedence, built-ins, and overloads |
| Patterns | case, match, bindings, and exhaustiveness |
| Errors | Assertions, panics, results, and propagation |
| Traits and impl | Methods, operators, capabilities, and laws |
Runtime and machine boundaries
| Topic | Contract |
| Ownership | Borrow, move, and allowance analysis |
| Memory | Runtime representation and storage boundaries |
| Runtime | Execution, cleanup, concurrency, and effects |
| Native | FFI, ABI, targets, and unsupported interfaces |
| NYC | C compiler driver, targets, and verification evidence |
| Nyr | Public low-level IR and object API |
| Linking | Object and symbol resolution support |
| Embedding | C embedding and VM APIs |
Compiler reference
Compiler architecture and compile-time facilities:
Reading a boundary
For backend-, target-, or source-shape-specific behavior, follow the owning page's implementation and fixture links. The status guide covers adoption and execution-route limits.