14.1 Pipeline overview
Resolution, assembly, parse, mods, semantic analysis, lowering, JIT or AOT.
Pipeline overview
Mirror of the normative Build pipeline overview—same flow, book voice.
flowchart TB resolve[Project resolution] assemble[program.assemble] parse[Parse and syntax diagnostics] mods[Mod host optional] semantic[Semantic rules and composition.resolve] hir[HIR resolve and type-check] lower[lower_program to CodegenArtifact] jit[JIT run_entrypoint] aot[AOT build and link] resolve --> assemble --> parse --> mods --> semantic --> hir --> lower lower --> jit lower --> aot
Crate map
Section titled “Crate map”| Stage | Primary crates |
|---|---|
| Resolution / graph | beskid_analysis (projects), beskid_cli |
| Parse / syntax | beskid_analysis (syntax, parser) |
| Mod host | beskid_analysis (mod_host) |
| Semantic rules | beskid_analysis (analysis) |
| Lowering | beskid_codegen |
| JIT | beskid_engine, beskid_runtime, beskid_abi |
| AOT | beskid_aot |
| Phase IDs | beskid_pipeline |
CLI entry
Section titled “CLI entry”beskid build, beskid run, beskid analyze orchestrate subsets—contract: Build / analyze / run.
Diagnostics parity
Section titled “Diagnostics parity”LSP analysis should match CLI phases for the same snapshot (LSP diagnostics).