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.
Use it to settle questions about source-level meaning before inspecting a compiler diagnostic or runtime implementation. Compiler and execution pages may explain how the rule is realized, but they do not replace this domain’s language-facing contract.
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.
Read claims at the right level
Section titled “Read claims at the right level”Use an area page to choose a subject, a feature hub to understand its scope and maturity, and the linked articles or requirements for detail. If a Book example is useful but incomplete, follow its platform-spec link rather than inferring an edge case from the example.
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.