Interton Patch Notes
Current documentation target: Interton beta-v_.7.4
This note describes user-facing changes visible in the current compiler, runtime behavior, examples, and documentation set. It intentionally avoids internal implementation details and code excerpts.
Fixed
- The current beta closes a number of practical gaps in day-to-day CLI usage by making execution modes and output behavior clearer and more controllable.
- Cross-language execution is easier to manage thanks to explicit runtime override flags for Python and Node foreign calls.
- JSON-line service-style execution is available for long-lived request/response flows instead of requiring one-shot command usage only.
- The callable runtime surface now covers more common JSON and process-integration scenarios, reducing the need for user-side workarounds.
- Documentation coverage has been repaired and consolidated around the actual current beta surface instead of leaving key areas scattered or implied.
Updated And Improved
- The language surface is broader than in the compared baseline and better reflects real application scenarios.
- Control flow now covers more dispatcher and recovery patterns, including
switch, richermatchusage, and structuredtry / catch / finallyflows. - Async syntax is exposed as a user-controlled feature via CLI toggles, so projects can explicitly enable or disable
async/awaitbehavior per run. - Module and foreign-language declarations are more flexible, including path-based foreign declarations with
from "...". - The standard callable surface is more practical, with JSON helpers, typed JSON access helpers, process-launch helpers, and richer input/output convenience functions.
- Mermaid-related functionality is substantially broader and more visible to end users, with a larger orchestration-oriented surface around clusters, struct-oriented generation, temporal and causal scenarios, and runtime metadata/reporting flows.
- Profiling and reporting are stronger and more export-friendly, making execution analysis and regression tracking easier.
Performance
- Compilation and execution workflows have received measurable optimization attention compared with the baseline line.
- The current toolchain exposes stronger profiling, timing, and report-generation support, which helps users observe performance characteristics more directly.
- The repository now contains a more mature performance-measurement workflow around compiler and runtime scenarios.
- Performance work is ongoing: the current line is faster and better instrumented than the compared baseline, and further optimization remains an active direction rather than a finished one-time change.
Documentation
- The user documentation set has been rebuilt around a compact handbook-style structure.
- The Russian track has been refreshed and consolidated around the current beta surface.
- A matching English track now exists under
docs/users/en, with the same compact structure and topic coverage as the Russian track. - The documentation now presents CLI behavior, Mermaid usage, library surface, and language rules as a coherent user-facing set instead of a fragmented collection of notes.
In Progress
- Some larger roadmap and design documents still describe a broader target state than what should be treated as fully validated today.
- Mermaid and orchestration-related work is already substantial, but the large design materials should still be read as a mix of implemented surface, planned direction, and ongoing refinement.
- Performance work is not considered complete; the current line includes improvements and better measurement infrastructure, but further speed-focused work is expected.