LEARN VOID / TOOLING & INTEGRATION
Live development
Keep a running idea alive while its implementation changes.
Why continuity matters
For interactive applications, restarting can mean rebuilding the scene, reproducing an input sequence or finding the state you were investigating. VOID’s live-development goal is to apply compatible function-body changes while keeping the running program under the developer’s control.
A compatibility boundary
Runtime integration already supports compatible function replacement and keeps old code alive while in-flight work still needs it. Changes to type layouts, function signatures or incompatible capture layouts cannot be treated as a simple body replacement.
What is planned
Automatic file watching and save-triggered replacement remain future work. The current runtime integration is not an automatically watching development command. Incompatible changes require a deliberate restart rather than a forced restart that silently discards a session.
Useful speed, measured
A delivered debug-cache subset can reuse compatible compiled artifacts after source validation. This is separate from live replacement and does not serialize live application state. Performance work should be judged through real edit/build/run workloads, not an invented timing claim.