Developers / Compiler-facing language reference

Compiler-facing language reference

Compiler changes should start from the language contract. The unsuffixed references listed below own syntax, semantics, edge cases and deferred language surfaces.

Canonical references

Each public route groups the references for one language area.

Foundations:

• Language basics
• Values and bindings
• Numbers
• Casts

Functions and control flow:

• Functions
• Branching
• Loops
• Errors, options and assertions

Data and compile-time construction:

• Structs
• Choices
• Collections and maps
• Templates
• Constants and compile-time behaviour

Names and static abstraction:

• Aliases
• Generics
• Traits

UI state:

• Reactivity

Projects and imported content:

• Project structure
• Packages and dependencies
• Resources and file values
• Moth template files
• Plain Markdown

Each route combines a Basic teaching layer with detailed Advanced references. The unsuffixed Moth template files form the canonical language authority. Basic files and route introductions teach that contract without replacing it.

Reference map

docs/src/developer-docs/language/overview.mtf lists every canonical file and routes formal compiler, build and memory ownership.

Related design

• Design scope, public authority: accepted mechanisms and intentionally excluded complexity
• Access and aliasing: shared reads, explicit copies and exclusive access
• Compiler design overview: stage ownership and cross-stage data flow
• Progress matrix: current implementation support and known gaps

More documentation

See All documentation for tutorials, examples and feature-focused language pages.