Stdlib family compiler
This family page is the encyclopedia entry for one stdlib area. It explains why the family exists, what responsibility belongs here, and which files make up the surface.
Overview
| Field | Value |
|---|---|
| Family | compiler |
| Module count | 27 |
| Purpose | Compiler-owned stdlib surfaces that support self-hosted compiler and driver integration. |
Architecture role
This family is not general-purpose business code. It exists to support compiler-owned flows where the compiler and stdlib need a shared contract.
Main responsibilities
- Keep compiler-facing library helpers clearly scoped.
- Avoid leaking compiler-specific surfaces into the general-purpose families.
- Document any ownership boundary between compiler internals and shared helpers.
Real usage story
- A self-hosted compiler flow can reuse structured helpers without pretending they are general stdlib entry points.
- A driver surface can depend on this family while still keeping its public contract documented elsewhere.
Module inventory
compiler/backends/ast/target_decl.vitcompiler/backends/ast/target_expr.vitcompiler/backends/ast/target_stmt.vitcompiler/backends/ast/target_type.vitcompiler/backends/backend.vitcompiler/backends/context/backend_context.vitcompiler/backends/emit/emit.vitcompiler/backends/lower/lower_mir.vitcompiler/backends/mod.vitcompiler/backends/runtime/vitte_runtime.vitcompiler/backends/tests/smoke.vitcompiler/backends/toolchain/arduino.vitcompiler/backends/toolchain/vitte_toolchain.vitcompiler/driver/compiler.vitcompiler/driver/mod.vitcompiler/driver/options.vitcompiler/driver/pipeline.vitcompiler/frontend/ast.vitcompiler/frontend/diagnostics.vitcompiler/frontend/lexer.vitcompiler/frontend/parser.vitcompiler/frontend/token.vitcompiler/ir/hir.vitcompiler/ir/lower.vitcompiler/ir/mir.vitcompiler/mod.vitcompiler/tests/smoke.vit