Compiler engineering learning route¶
Inspect each representation before moving to the next stage. These lessons distinguish semantic analysis, planning, numeric control transformation and public reference compilation. They do not submit hardware work.
| Lesson | Run from the repository root | What you will inspect |
|---|---|---|
| Beginner: syntax and HIR | python3 examples/user/tracks/compiler_engineer/01_beginner_syntax_hir_en.py |
Symbol, unit and capability checks without executing the function body. |
| Graph and plan | python3 examples/user/tracks/compiler_engineer/02_foundation_hybrid_graph_plan_en.py |
Dependency order and the additional payload bindings needed by a bundle. |
| Parameter projection | python3 examples/user/tracks/compiler_engineer/03_applied_parameter_projection_en.py |
Actual projected values and the difference between reuse and recompilation. |
| Validation and discretization | python3 examples/user/tracks/compiler_engineer/04_advanced_validation_discretization_en.py |
Changed values, units, paths and strict-grid diagnostics. |
| Expert: reference compilation | python3 examples/user/tracks/compiler_engineer/05_expert_reference_compile_provenance_en.py |
Pass records, source mapping, target references and actual cache status. |
All five examples stop before numerical or hardware execution. Building a bundle proves payload binding, not that every later consumer's requirements are met. Parameter projection updates semantic arguments without binding numerical payloads. Reference compilation reports no private calibration, hardware payload or production scheduling.
For complete interfaces, see Hybrid syntax, Hybrid parameters, validation and discretization and limitations.