Source and checking
.zi modules, imports, procedures, records, applied generic records, enums, fixed arrays, borrowed slices, constants, and selected compile-time forms. Unsupported source forms are diagnosed.
Status / Experimental
What works today.
Ziran has a functioning, tested core. It is not yet a complete implementation of its language direction or a stable 1.0 platform. This summary follows the current implementation status; consult that file for feature-level details.
Native output
A shared frontend produces C, C++, and native Go for tested non-UI programs. Saved .zir modules can be rechecked and compiled by these targets.
Portable bundles
.zib links and runs checked scalar, string, record, enum, fixed-array, slice, and declared host-capability programs within documented limits. It does not run every checked program.
Standard library
Text, UTF-8 scanning, JSON scanning, generic value records, experimental Vec(T) storage and a string builder, plus explicit process and HTTP host contracts. Coverage is still growing.
Still required
The next boundaries
Language coverage
Complete Jai syntax compatibility, general procedure values, and broader ownership coverage.
Backend equivalence
Make structured .zir authoritative across every checked expression and finish C, C++, Go, FFI, and portable behavior parity.
Portable effects
Broaden the .zib verifier and execution coverage, host handles, arrays, and capability contract.
Laws and parallel execution
Design and implement proof-oriented law checks, automatic CPU parallelism, and a GPU backend. These are not current capabilities.
Kryon integration
Complete platform hosts, renderer behavior, and downstream application cutover to Ziran-based Kryon.