EN Runtime Model

Runtime Model | مدل اجرا

Plix has two execution paths with the same language semantics:

Interpreter | مفسر

plix run app.px

The interpreter is the fastest feedback loop. Use it while exploring syntax, debugging a small function, or reading diagnostics. It avoids a native link step and is ideal for examples and tests.

Native compiler | کامپایلر native

plix build app.px -o app
./app

The native backend lowers typed and checked code through Cranelift and links it with the Plix runtime. Use it for distributable executables, performance measurements, and deployment-oriented checks.

A useful discipline | روش پیشنهادی

1. plix check — parse, type-check, and ownership-check.
2. plix run — confirm behavior quickly.
3. plix build — verify native code generation and linking.
4. Compare observable output when changing low-level code.

The repository's release battery performs this comparison automatically for examples, guards, fuzz inputs, and negative programs. If interpreter and native behavior differ, treat it as a compiler/runtime defect rather than adjusting the example to hide the difference.

Runtime responsibilities | مسئولیت runtime

The embedded runtime provides tagged values, heap services, standard-library services, networking support, and optional Python FFI. Native code calls runtime symbols through the frozen ABI described in ABI_CHANGELOG.md.

---

Learning path: ← Error Guide · Compiler Development →