Documentation

Start with the short tutorial or the exercise course; guides describe the current surface. References are checked against source. Policy pages distinguish current limits from proposed 1.0 promises.

Learn in order

Learn Fibber the Hard Way is a practice-first route through 16 exercises plus setup: type, predict, change, break and repair programs, then ship a tested file-processing command. The short tutorial below is a tour.

• Install and hello
• Values and collections
• Functions and types
• Ownership by example
• A project
• Concurrency
• Ship a program

Task guides

• Concurrency and parallelism
• Errors, traps and try
• GPU kernels
• Macros
• Modules and namespaces
• Numerics, SIMD and tensors
• Ownership and borrowing
• Packages and dependencies
• Protocols, records and enums
• Targets and deployment
• Testing
• Tooling
• Unsafe FFI and drivers

Reference

• Diagnostics
• File formats
• Language reference
• CLI commands and flags
• Builtin signatures
• Environment inventory
• Library facade declarations
• Compiler target table

Policy and limits

• Known limits and security boundaries
• Platform support and evidence
• Stability and the 1.0 proposal

Internals and history

• Design index: dated proposals and implementation evidence.
• ADRs: executable architecture decisions.
• Compiled lIR objects: proposed native-object caching and linking into one executable.
• Specification: normative rules; stdlib planning rows are labelled.
• History/source map, Rust retirement.
• Examples, contributing.