13.2 Language meta map
User-visible Beskid law—syntax, types, contracts, memory, evaluation, interop.
Language meta map
Language meta is language law: what valid programs mean, independent of which Rust crate happens to implement it today.
Major areas (reading order for newcomers)
Section titled “Major areas (reading order for newcomers)”| Area | You learn |
|---|---|
| Program structure | Modules, names, imports, extend |
| Type system | Types, generics, conformances |
| Contracts and effects | contract, Result, testing |
| Memory model | Locals, ref, heap, GC rules |
| Evaluation | Closures, fibers and spawn |
| Interop | extern, ABI profiles |
| Metaprogramming | Mod SDK surface (Beskid-side) |
| Conformance | Glossary, normative vocabulary |
Articles vs hubs
Section titled “Articles vs hubs”- Area pages index features (tiles).
- Feature hubs bundle articles, ADRs, optional graphs.
- Articles (
specLevel: article) carry the MUST/SHOULD prose.
Linking from the book
Section titled “Linking from the book”When this book says “the compiler will reject that,” the receipt is usually a language-meta diagnostic band (e.g. E16xx contracts, spawn capture rules)—not a blog post.