14.5 JIT run
beskid_engine run_entrypoint, JIT modules, and quick iteration.
JIT run
JIT is the “run what I just compiled” path: artifact in memory, entrypoint invoked through beskid_engine.
Crates
Section titled “Crates”| Crate | Role |
|---|---|
beskid_engine | run_entrypoint, module registration, extern validation |
beskid_runtime | Builtins, GC hooks, fiber scheduler |
beskid_abi | Symbol tables, version exports |
Spec: Backends JIT/AOT, Program assembly.
beskid run --project path/to/Project.projBehavior must match analyze/build resolution (CLI contract).
When JIT is enough
Section titled “When JIT is enough”- Local dev loops, scripting targets, compiler dogfooding.
- Tests that execute generated code in-process.
When JIT is not enough
Section titled “When JIT is not enough”Shipping binaries, mod AOT registration, or deployment without a compiler on the target → AOT build.