A technical report states one part of the design completely: the model it rests on, the mechanisms that implement it, the guarantees that follow, and the costs that are paid for them. Where a Learn article shows a feature at work and the Reference states exact rules, a report explains why the whole hangs together - deeply enough to reason about a program’s behavior from first principles, and without assuming a compiler background.
Reports are numbered and dated. A revised report keeps its number and carries its revision date; the facts it states are true of the compiler at the commit it names.
| Report | Subject |
|---|---|
| TR-1 - Memory management in Mica | regions, ownership, and the value model: where every byte lives, who reclaims it, and what the compiler proves about it |