Beta 1
Note
This page is the historical Beta 1 capability assessment (Phases 117–118). The current public label is Karkain 1.2.0 (Stable) — see Release Notes and Compatibility Policy for the current release identity and guarantees.
Karkain Beta 1 was the first release focused on making the implemented language core and developer toolchain dependable enough for broader developer experimentation. This page defines exactly what Beta 1 promises — and what it deliberately does not.
What Beta 1 means
Beta 1 is a maturity statement about the implemented core, not a claim that every roadmap feature exists:
Property |
Meaning |
|---|---|
Implemented features |
Real, exercised by gate tests through the actual pipeline. |
Stable enough to rely on |
The stable core behaves consistently across documented workflows and engines. |
Consistent across workflows |
|
Protected by regression tests |
Every claim below is backed by a gate (conformance corpus, Golden example corpus, parity tests, CLI E2E tests). |
Clearly documented |
Status vocabulary, exit-code contract, error codes and known limitations are all documented on this site. |
Features outside the stable core remain classified as Implemented, Experimental or Planned. Nothing listed there is silently presented as Beta stable.
The Beta 1 stable core
The following surface is the Beta 1 stable core. Both engines (the Go front
end and the self-hosted kcc) accept and run these features with
byte-identical output on the golden corpus.
Language
Variables (
let/var/const), functions, recursion, control flow (if/else,while/C-stylefor/for-in,break/continue/return), assertions.Primitive types and values: integers, floats, booleans, strings,
None; checked division/modulo/indexing withruntime error: <kind> at <file>:<line>.Arrays, maps, structs (records), enums and
match, module imports withpublicexports and qualified calls.
Toolchain
karkain check | build | run | test | fmt | lint | debug | prof | target | explain | clean | pkg | lsp.Stable exit-code contract: 0 success, 2 usage error, 3 compile/parse/ semantic failure, 4 failing tests, 5 invalid/incompatible engine, 6 environment/toolchain failure, 7 lint findings, 1 runtime failure.
Two engines with parity gates: Go front end (default development engine) and the self-hosted
kcc(default engine forcheck/build/run/testthrough the CLI).Runtime error diagnostics and stack traces are byte-identical on both engines.
Standard library
The public stdlib modules are std.string, std.collections,
std.io, std.encoding and std.crypto (plus std.testing just
for tests). std.encoding/std.crypto are backed by byte-level runtime
builtins verified against NIST FIPS 180 and RFC 4648 test vectors.
Examples
The example corpus (Phase 114/116: 49 pinned golden examples plus the
developer/real-world categories) is regression-gated: every Runnable
example carries a header declaring its engine and every golden is asserted
byte-identical on every run.
Compatibility expectations
Stable core: changes are deliberate, documented and accompanied by a regression test. Breaking the published stable surface requires a documented justification.
Experimental: may change without notice. Read the specific experimental page entry to know exactly why it is experimental.
Planned / Not Yet Implemented: no compatibility guarantee — nothing exists yet.
Beta 1 is not Karkain 1.0. No Stable/Production Ready/1.0
claim is made, and the compatibility policy is intentionally lightweight
until a release candidate establishes a full 1.0 matrix.
Known limitations (honest list)
Engine boundaries — concurrency, profiling, debug tracing, WASM and SIMD vector types are Go-engine only;
kccparity for those surfaces is a documented post-Beta boundary, never silently claimed.Closures / function values —
fncodegen is not supported on either engine (documented Phase 101 boundary); no gate pretends it works.Syntactic gate — unparenthesized
whileconditions were removed from the official surface in Phase 117 (both engines now accept them via the Phase 117 parser alignment, but the documented form remainswhile (cond)).Cross-compilation — real cross-linkers (GNU cross-gcc/clang
--target) are required for foreign triples; on a host without one,karkain build --target <foreign>fails deterministically with a toolchain error. Thewasm32-wasitarget requireswasmtimeto run.Bootstrap memory — full
kccbuild mode for the compiler’s own sources can stall on very memory-limited hosts; the low-memorycheckpath passes everywhere (documented environmental limitation, not a defect).Package manager — local/workspace resolution and lockfiles are real; there is no public registry.
Feedback expectations
Beta 1 exists to gather feedback on the implemented core. Report issues,
incorrect diagnostics, engine divergences and missing documentation at the
project repository. Before opening an issue, reproduce with the current
karkain.exe and quote the exact diagnostic.
See also
Status — the six-level status vocabulary used everywhere on this site. Developer Preview — the honest capability summary that preceded Beta 1. Implemented — every implemented feature with its gate. Experimental — features that exist but are not stable. Planned — designed but not implemented. Roadmap — the planned surface over time.