diff --git a/Release Notes/_index.json b/Release Notes/_index.json index 10b990c76..1178faa5f 100644 --- a/Release Notes/_index.json +++ b/Release Notes/_index.json @@ -6,6 +6,11 @@ "type": "ContentText", "body": "
Io uses date-based versioning. This page collects the notable changes of the last twelve months — a period in which the VM was rewritten around a stackless evaluator and re-targeted from native binaries to WebAssembly. Entries marked tagged correspond to release tags in the repository; the rest are development milestones on the road between them. For the longer arc, see the Timeline.
" }, + { + "type": "ContentText", + "title": "2026.11.18 — Long-running programs stop growing", + "body": "Tagged 2026.11.18. A memory fix for programs that never return to the top level: servers, actors, and long-lived coroutines.
while, loop, for and foreach kept every value a loop body created until the enclosing method returned, so a top-level script or an actor that loops forever grew without bound. A 300,000-iteration loop used to leave 300,000 objects behind; it now leaves two (#513).yield, pause or resume left a stray marker on the retain stack that kept a few objects alive per switch.for and foreach — loops counting through small integers released the wrong retain-stack entries on each iteration, which could corrupt the stack.Notable changes in Io over the past twelve months.
Io uses date-based versioning. This page collects the notable changes of the last twelve months — a period in which the VM was rewritten around a stackless evaluator and re-targeted from native binaries to WebAssembly. Entries marked tagged correspond to release tags in the repository; the rest are development milestones on the road between them. For the longer arc, see the Timeline.
Tagged 2026.11.17. The first release since the WASM merge, and the first on npm.
npm install @iolanguage/io runs the VM from JavaScript in Node and browsers (@iolanguage/io). Releases publish to npm from the release workflow with provenance.wait and await on JS Promises run without blocking JavaScript; an eval that waits resolves when it finishes, and callbacks JS calls later can wait too (#509).Io.load(), eval, lobby, onOutput, dispose (#507).x := ( raises a catchable compile error; it used to trap the VM and end a REPL session (#511).then/catch/finally ran the rest of the statement twice; JS Promises stopped resolving after about a thousand; List_removeLast_ never removed anything, so retained objects were never released.make component builds the VM as a WebAssembly component (wasm32-wasip2) alongside the core WASI module.wait parks the calling coroutine on a timer queue instead of busy-spinning; timed coroutines run concurrently and the VM idles in a single host wait until the next deadline.future/stream) once host and toolchain support land.Tagged 2026.04.20-native-final. The WASM branch merged to master (#495); WebAssembly/WASI is now the default and only build target. The final native build — CMake, Eerie, and DynLib — is frozen at this tag, with ongoing native work on the native branch.
Vector primitive gains a WebAssembly SIMD128 backend, restoring AltiVec-era vector acceleration on modern hardware and in the browser.Map implements comparison for equality (#28).asJson added to nil, true, and false (#27).isKindOf fix — ancestor checks use identity comparison (#201).Tagged 2026.03.06-stackless-alpha. The first alpha of the stackless VM, together with the initial WebAssembly port and a new JavaScript integration model.
BigInt — arbitrary-precision integers with transparent round-tripping across the Io↔JS bridge.The recursive, C-stack-based evaluator was replaced with a heap-allocated frame state machine — the foundation the WASM port builds on. With no native C stack to switch, the platform-specific coroutine assembly is no longer needed.
callcc, behind the IO_CALLCC build flag).if branches.setjmp/longjmp.signal / withHandler: a handler can resume at the signal site, fall through, or unwind.Native ARM64 coroutine support for Apple Silicon and modern Linux (#476) — the last major addition to the native-era coroutine implementation before the stackless rewrite made platform-specific coroutine code unnecessary.
Notable changes in Io over the past twelve months.
Io uses date-based versioning. This page collects the notable changes of the last twelve months — a period in which the VM was rewritten around a stackless evaluator and re-targeted from native binaries to WebAssembly. Entries marked tagged correspond to release tags in the repository; the rest are development milestones on the road between them. For the longer arc, see the Timeline.
Tagged 2026.11.18. A memory fix for programs that never return to the top level: servers, actors, and long-lived coroutines.
while, loop, for and foreach kept every value a loop body created until the enclosing method returned, so a top-level script or an actor that loops forever grew without bound. A 300,000-iteration loop used to leave 300,000 objects behind; it now leaves two (#513).yield, pause or resume left a stray marker on the retain stack that kept a few objects alive per switch.for and foreach — loops counting through small integers released the wrong retain-stack entries on each iteration, which could corrupt the stack.Tagged 2026.11.17. The first release since the WASM merge, and the first on npm.
npm install @iolanguage/io runs the VM from JavaScript in Node and browsers (@iolanguage/io). Releases publish to npm from the release workflow with provenance.wait and await on JS Promises run without blocking JavaScript; an eval that waits resolves when it finishes, and callbacks JS calls later can wait too (#509).Io.load(), eval, lobby, onOutput, dispose (#507).x := ( raises a catchable compile error; it used to trap the VM and end a REPL session (#511).then/catch/finally ran the rest of the statement twice; JS Promises stopped resolving after about a thousand; List_removeLast_ never removed anything, so retained objects were never released.make component builds the VM as a WebAssembly component (wasm32-wasip2) alongside the core WASI module.wait parks the calling coroutine on a timer queue instead of busy-spinning; timed coroutines run concurrently and the VM idles in a single host wait until the next deadline.future/stream) once host and toolchain support land.Tagged 2026.04.20-native-final. The WASM branch merged to master (#495); WebAssembly/WASI is now the default and only build target. The final native build — CMake, Eerie, and DynLib — is frozen at this tag, with ongoing native work on the native branch.
Vector primitive gains a WebAssembly SIMD128 backend, restoring AltiVec-era vector acceleration on modern hardware and in the browser.Map implements comparison for equality (#28).asJson added to nil, true, and false (#27).isKindOf fix — ancestor checks use identity comparison (#201).Tagged 2026.03.06-stackless-alpha. The first alpha of the stackless VM, together with the initial WebAssembly port and a new JavaScript integration model.
BigInt — arbitrary-precision integers with transparent round-tripping across the Io↔JS bridge.The recursive, C-stack-based evaluator was replaced with a heap-allocated frame state machine — the foundation the WASM port builds on. With no native C stack to switch, the platform-specific coroutine assembly is no longer needed.
callcc, behind the IO_CALLCC build flag).if branches.setjmp/longjmp.signal / withHandler: a handler can resume at the signal site, fall through, or unwind.Native ARM64 coroutine support for Apple Silicon and modern Linux (#476) — the last major addition to the native-era coroutine implementation before the stackless rewrite made platform-specific coroutine code unnecessary.