Open Manual

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

TopicContract
UnitsFiles, imports, modules, and entry points
SyntaxSource forms and grammar
ValuesLiterals, containers, equality, and value operations
TypesType forms, inference, refinements, and proofs
Dependent types and indexed dataRefinements, Pi and Sigma types, GADTs, first-class Type values, type-level functions, and runtime indices
Kernel, erasure, and soundnessTrusted core rules, the erasure and ABI model, and the soundness risk register
FunctionsCalls, parameters, closures, and function contracts
Control flowBranches, loops, exits, cleanup, and error handling
OperatorsPrecedence, built-ins, and overloads
Patternscase, match, bindings, and exhaustiveness
ErrorsAssertions, panics, results, and propagation
Traits and implMethods, operators, capabilities, and laws

Runtime and machine boundaries

TopicContract
OwnershipBorrow, move, and allowance analysis
MemoryRuntime representation and storage boundaries
RuntimeExecution, cleanup, concurrency, and effects
NativeFFI, ABI, targets, and unsupported interfaces
NYCC compiler driver, targets, and verification evidence
NyrPublic low-level IR and object API
LinkingObject and symbol resolution support
EmbeddingC 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.