Migration to Beta 1
Karkain moved from Developer Preview to Beta 1 in Phase 117. This page explains what actually changed for a developer who was using the Developer Preview line (v0.115.x) and what they must do to move to Beta 1 (v1.0.0).
Developer Preview vs. Beta 1
The public label changed from Developer Preview to 🧪 Beta 1. The
version identity changed from v0.115.0 (... Developer Preview Build) to
v1.0.0 (... Stable Build).
Are there source-breaking changes?
No source-breaking changes were introduced by the Developer Preview to Beta 1 transition. Programs written for the Developer Preview language core continue to parse, type-check and run on Beta 1 through both engines.
What changed (Phase 117)
Area |
Change |
|---|---|
Parsers |
The Go parser and the self-hosted |
Semantic build/run gating |
|
Recoverable parse errors |
Parse errors are no longer swallowed by |
Workspace dependency resolution |
|
Error-code documentation |
Numeric error codes (K001–K008, K100, K101–K113) are documented by
|
Standard-library edge cases |
Stdlib edge-case parity (e.g. UTF-8, malformed hex/Base64) is now gated on both engines. |
Example corpus |
The corpus grew to 50 |
Documentation |
The Beta 1 capability assessment (Beta 1), the status vocabulary and the release notes were rewritten for the Beta label. |
Fresh-checkout validation |
A reproducible fresh-checkout validator
( |
Language surface
The Beta 1 stable core (see Beta 1 and
Stable API Snapshot (1.2.0)) is the same language surface external
developers were already using in the Developer Preview: variables,
functions, control flow, structs, enums, modules, and the five importable
std.* modules. No language syntax was removed.
Known material limitations carried over
Closures /
fnfunction values: codegen is not supported on either engine (documented Phase 101 boundary).Concurrency, profiling, debug tracing, WASM and SIMD are Go-engine only;
kccparity is a documented post-Beta boundary.There is no public package registry; the package manager resolves local and workspace dependencies.
Moving a Developer Preview project
Rebuild the toolchain from source (see Installation).
karkain –version reports
Karkain Compiler v1.2.0.Re-run your existing programs with
karkain check/run— no source changes should be required.If you used the workspace dependency path, verify cross-member calls now resolve (Phase 117 workspace dependency fix).
Re-run
karkain fmt --checkand the test suite to confirm formatting and behavior are unchanged.
See also
Beta 1 — the Beta 1 capability assessment. Compatibility Policy — the compatibility policy. Release Notes — what shipped in each release.