Release Notes
This page tracks the honest development state of Karkain. The toolchain is a Karkain 1.2.0 (Stable) build: functional, tested, and self-hosted. The v1.2.0 identity is the public label from the v1.2.0 release (1.0.x and 1.1.0 continue as historical lines); the 1.1.0 and 1.0.0 stories are preserved below as history.
Versioning: the CLI reports Karkain Compiler v1.2.0 via
karkain --version; the public label progressed Developer Preview (115,
v0.115.x) -> Beta 1 (117-118, v0.117.x) -> 1.0.0 (Stable) (Phase 119) ->
1.1.0 (Stable) (Phase 142) -> 1.2.0 (Stable) (Native Independence).
v1.2.0 - Native Independence (current)
Status |
Karkain 1.2.0 (Stable) - the project’s public status. Full story:
|
Theme |
Sovereignty I - Off C, Off Go. The native targets are emitted by the
SELF-HOSTED compiler, not by a C compiler and not by the Go backend:
|
What shipped |
The native VALUE MODEL in the self-hosted engine: arrays, the heap arena, string operations (concat, push, records, maps) and float64. The self-hosted engine’s own machine-code ENCODER, the ELF, PE and Mach-O container writers, and the whole-program driver. The native milestones, each with its own gate: NAT-CALL (user functions), NAT-IF (branches), NAT-QUAL (the qualification), NAT-LOOP (loops, break/continue), NAT-IDX (array indexing and the bounds diagnostic), NAT-FRAME (the frame layout against the Go oracle’s), NAT-STR-STAGE (the string staging area), NAT-RODATA (the reporter’s read-only data) and NAT-REG (register allocation, opt-in). |
Compatibility |
Every 1.1.0 program builds and runs identically. The surface change is strictly additive; the one behavioural change is that the native targets are now produced by the self-hosted engine. |
Release provenance |
The 13 published archives were built locally on a Windows host
from the tagged commit ( |
Known differences |
The reporter’s read-only data is laid out in the oracle’s interning
order except for one shape, and the field-assignment code differs by 25
bytes because the oracle stages the pair through the string staging area
and the self-hosted driver does not. Both are documented in
|
v1.1.0 - Stable Build (historical)
Status |
Karkain 1.1.0 (Stable) — the project’s public status; 1.0.x is the
LTS line (security fixes). Full story:
|
Since 1.0.0 |
Stdlib freeze + SemVer policy (132); first-class |
Compatibility |
Every 1.0.0 program builds and runs identically (conformance 64/64, Phase 114 corpus byte-identical Go↔kcc); the one behavior fix is K114 escape rejection (previously accepted-and-miscompiled) |
Example corpus |
61 files across 15 categories (59 Runnable incl. test-mode, 2 Stable, 1 Planned dir), pinned goldens byte-identical both engines |
v1.0.0 — Stable Build (historical)
Status |
Karkain 1.1.0 (Stable) — the project’s public status (see Compatibility Policy for the guarantees attached to it) |
Language core |
Stable core defined and regression-gated on both engines: variables,
functions, recursion, control flow, arrays, maps, structs, enums,
match, strings, modules with |
Diagnostics |
Recoverable parse errors are no longer swallowed by |
Error codes |
Numeric codes (K001-K008, K100, K101–K115) documented by
|
Standard library |
Public modules hardened: |
Example corpus |
|
Self-hosted compiler |
|
Bootstrap memory guard |
|
Compute targets |
|
Toolchain |
|
Developer readiness |
|
Known gaps (honest) |
|
Entry requirements for every release note entry
The CLI version reported by
karkain --version.What is newly Implemented (gated) vs experimental vs planned.
Any behavior changes that might break existing programs.
Previous highlighted milestones
Phase |
Version era |
Summary |
|---|---|---|
117 |
v0.117.0 |
Beta 1 readiness (historical): Go/kcc |
116 |
v0.115.0 |
Corpus normalization + real-world programming examples (50 files, dash-named categories, stack/queue/knapsack/token-stats) + metadata gate |
115 |
v0.115.0 |
Developer Preview readiness: license/contributing/CoC, honest docs, version identity, fresh-checkout gate |
114 |
pre-0.115 |
Example corpus (46 files, 15 categories) + parity gate |
113 |
pre-0.115 |
Developer Preview documentation + status model established |
111 |
pre-0.115 |
Cross-compilation via explicit target triples |
107–110 |
pre-0.115 |
Concurrency runtime, WASM target, standard library v2, profiling |
95–99 |
pre-0.115 |
Self-hosted compiler becomes the default engine; bootstrap identity |
91 |
pre-0.115 |
(Historical note: this phase claimed a “1.0 release-ready” decision; that claim was retracted — the label moved Developer Preview → Beta 1 → 1.0.0 at Phase 119.) |