13.3 Compiler domain map
Build pipeline, front-end, semantic pipeline, mods, conformance, and implementation map.
Compiler domain map
Compiler documents the reference compiler workspace—phases, diagnostics parity, and mod host contracts—without redefining language semantics.
Areas worth bookmarking
Section titled “Areas worth bookmarking”| Area | Contents |
|---|---|
| Build pipeline | Resolution → parse → mods → semantic → lower → JIT/AOT |
| Front-end | Grammar, parser, AST/HIR contracts |
| Semantic pipeline | Rules, diagnostic registry |
| Resolution and projects | Graph, workspaces, cycles |
| Compiler mods | Mod host bridge, syntax facade, scheduling |
| Conformance | beskid_tests policy |
| Implementation map | Crate anchors |
Workspace crates (quick)
Section titled “Workspace crates (quick)”From compiler/Cargo.toml members most readers touch:
beskid_analysis— parse, resolve, semantic rules, mod hostbeskid_codegen— lowering toCodegenArtifactbeskid_engine— JITrun_entrypointbeskid_aot— AOT build and linkbeskid_cli— commandsbeskid_pipeline— shared phase IDsbeskid_tests,beskid_e2e_tests— conformance
Pipeline composition
Section titled “Pipeline composition”Rust-only host composition (IoC) is not Beskid mod syntax—see Pipeline composition.