Reference

Reference pages state the current compiler contract without tutorial narration. For a progressive introduction, start with Learn Kinmokusei.

GlossaryStorage, identity, failure, task, module, and Go-boundary vocabulary used across the site.CLICommands, options, outputs, side effects, and exit status.Language syntaxDeclaration and statement forms with current implementation boundaries.Type systemRepresentations, identity, assignability, copy/alias behavior, and nullability.OperatorsPrecedence, associativity, valid operands, evaluation, and failure behavior.Built-insCollections, allocation, array conversion, channels, Result, and Task forms.Standard modulesThe compiler-managed kinmokusei/http API and runtime contract.C FFI manifestSchema 1 calls, types, ownership, callbacks, handles, and thread policy.Go interop matrixSupported declarations, type shapes, operations, targets, CGO, and unsafe policy.Project fileskinmokusei.toml, kinmokusei.lock, targets, dependencies, and unsafe policy.DiagnosticsJSON schema, positions, streams, categories, and process status.CompatibilityToolchains, platforms, Go package connectivity, C boundaries, and generated Go.Implementation statusSupported features, release availability, and safety boundaries.

Status vocabulary

• Implemented is accepted by the compiler and covered by automated tests.
• Experimental is implemented but carries an explicitly provisional pre-1.0 contract.
• Unreleased is implemented on the development branch but is not available in the latest published compiler.
• Unsupported is deliberately rejected in the current compiler.

When a guide and a design note disagree, implementation and automated tests are the behavioral source of truth. The public docs describe implemented behavior only.