Language forms#

Every surface form of the language has a feature contract in docs/language/features/. A filled contract answers the same ten questions for its form: lexical and grammar rules; scope and binding; type and quantity requirements; effects, totality and evaluation order; elaboration into core; representation and target support; error codes and their origins; formatting and migration; positive, negative, execution and edge-case tests; and compatibility with the previous edition, serialized forms and cache keys. This index is generated from those files when the site is built.

The specificationReference · normativeSpecificationThe normative language semantics and trusted boundary. remains the normative definition of the language; a contract states how one form meets it. The language referenceReference · generatedLanguage referenceExact forms, quantities, effects, interfaces, and artifacts. lists which compiler module owns each form's syntax, static semantics and erasure, and whether the form reaches a native artifact today.

Contracts (31)#

Forms added or changed since the contract system began, plus overview contracts that tie several forms together. draft-alpha-2027 forms belong to the draft edition: preview a module's rewrites with alpha migrate --from alpha-2026 --to alpha-2027 --check.

Inherited forms (50)#

These forms were accepted in alpha-2026 before contracts existed. Their behaviour is covered by the edition conformance suite tests/alpha-tests; their syntax and owners are in the grammar and the reference. A change to one of them replaces its stub with a filled contract and a form-specific suite.