Language

This section owns Incan source: syntax, semantics, patterns, and the mental models behind .incn programs. Start from what you are trying to learn or build; use the navigation taxonomy only when you already know the page type you need.

Choose a route

FundamentalsRead the Incan BookLearn values, functions, control flow, errors, models, traits, and tests through small runnable chapters. CumulativeCarry one project through the languageApply functions, results, modules, tests, locking, and native builds to one typed workflow step. PackageBuild a library boundaryChoose an explicit public surface, build its checked artifact, and run a locked-workspace consumer. Native boundaryBuild a checked C bindingUse the experimental checked-C surface when a governed native ABI is the right boundary. Background bridgeTranslate what you already knowChoose the Python, Rust, TypeScript/JavaScript, or automation route from the Learn hub.

Recommended learning sequence

1. Complete Getting Started so the compiler, project, tests, and release build all work.
2. Use the Book for syntax and fundamentals.
3. Follow the guided project spine or choose a representative project tutorial.
4. Keep how-to guides and the generated language reference as lookup surfaces.

Choose the kind of answer

TutorialLearn by completing an outcomeUse a staged, release-envelope executable project when you want the reasoning and sequence together. How-toSolve a focused taskUse recipes for errors, files, JSON, async work, modules, tests, collections, and Rust interop. ReferenceLook up the contractUse generated syntax, type, built-in, derive, and standard-library surfaces when you know what to find. ExplanationUnderstand why it works this wayRead the mental models behind compilation, errors, modules, models, traits, and Rust-shaped confidence.

Common lookup points

• Feature inventory
• Error handling
• Models and classes
• Imports and modules
• Async programming
• Rust interop
• Checked C bindings
• Web framework
• Standard library index

For installation, projects, commands, editor support, reports, and CI, continue to Tooling. RFCs remain design records for contributors, not a prerequisite for learning the language.

The typed data processor, typed API, async worker, and external Rust crate are executable 0.5 projects. Standard-library work reuses the full toolchain Loaf; project-specific dependencies enter through an explicit Oven bake rather than a hidden Cargo fallback.