Repository navigation
Compiler Development
Arena Agent edited this page Sep 18, 2026
·
1 revision
The lexer turns source into tokens; the parser builds the AST; semantic checking validates types, ownership, scopes, and language rules.
The interpreter executes the checked representation directly. The native backend lowers it to Cranelift IR and links the runtime. Changes affecting either path should include a parity test.
Exported plix_* symbols, calling conventions, and value representation are tracked separately from the public language API. Read ABI_CHANGELOG.md before changing runtime boundaries.
Use the repository commands in CONTRIBUTING.md, including Rust checks, the release test battery, negative programs, and deterministic parity fuzzing. Keep a failing case small and add it to the appropriate suite.
- Getting Started
- Installation
- Language Reference
- Types and Ownership
- Structs and Traits
- Modules and Projects
- Standard Library
- Error Guide
- Runtime Model
- Architecture
- Compiler Development
- Testing and Tooling
- Cookbook
- Python FFI
- FAQ
- Contributing