The reference

Exhaustive, read by lookup: every construct v0.4.0 accepts, with its spelling, its semantics, its known limit and a whole program that proves it. What the language refuses is here too — as a page of its own and as the catalogue of every message.

Every fenced teko example on these pages is compiled and run by ../../scripts/check-docs.sh, and its // expect-exit: N header is the assertion. Most of them are derived from the fixtures in tests/, which the five native CI legs run on every push.

pagecovers
types.mdthe scalars, teko's seven aliases, f32/f64, ptr/uptr/str, struct, class, members, modifiers, static, const
classes.mdinheritance, the implicit receiver, base, constructors and destructors, abstract, interfaces, traits, properties, operators, partial, free order of declaration
generics.mdclass Box<T, const N: i64>, instantiation and mangling, inline array fields, partial generics
delegates.mddelegate, contextual and explicit values, the null panic, lambdas, use (...) by value and by reference
arrays.mdfixed arrays local, global and inline; the heap T[], its run-time index guard and its counted elements
namespaces.mdnamespace, using, import, how a bare name resolves, internal
control-flow.mdif, loop/break N/continue N, while, do, for, foreach, both switch spellings, the ternary
parameters.mddefault arguments, overloads, ref/out, params
di.mdthe three lifetime markers, inject, constructor injection, scope { }
memory.mdthe arena, reference counting per scope, ownership, destructors, panics
runtime.mdeverything lib/rt.tk exports, by signature
build.mdteko build, teko limits, teko.toml, mc.toml, the fixed point
diagnostics.mdevery teko: … message, by family, with cause and fix
not-yet.mdwhat v0.4.0 refuses, and the message each refusal answers

Start at types.md if you are reading in order; the guide is the task-oriented route, and ../specs/ holds what is designed and not built.

Edit this page