Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Dada and this model

Dada explores ownership through operations that give values, share ownership, and borrow access. Its goal is a Java-like object model with Rust-like control of storage and lifetimes: programmers describe objects and their relationships without requiring every object to occupy its own allocation.

The book is organized into language layers:

  1. Given begins with operational semantics for unique ownership, followed by a type system that tracks initialized, empty, and unknown places with views and proves progress and preservation.
  2. Shared adds operational semantics for shared ownership. Its type-system chapter is coming.
  3. CFlow reserves the next part for control flow.

Each language has its own syntax, execution rules, examples, and invariants. A correspondence theorem shows that the translation of a Given program has exactly its original execution behavior in Shared. The checked operational models cover construction and fresh-variable bindings. Given also contains an unpacking extension used by the typing chapter. Its operations and structural preservation are checked, as are static progress and preservation for the Given type system. Assignment, drop, primitives, function calls, and borrowing remain outside these models.

Later chapters will add features to this foundation one layer at a time. The design goals explain the choices the model is intended to support.

The prose and mathematics stand on their own. A Lean selector reveals the associated formal definition, theorem, or example. Lean checks proofs; recorded reviews compare their statements with the explanation. The contributor guide describes that process.