From e4d075af6c5e14f4a0960ef08e7ed0c2aaf16e12 Mon Sep 17 00:00:00 2001 From: Lilleman auf Larv Date: Mon, 28 Sep 2026 18:56:07 +0200 Subject: [PATCH] Name the hold set in the decision's first line --- docs/decisions.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/decisions.md b/docs/decisions.md index 56d0024..e7ea0bd 100644 --- a/docs/decisions.md +++ b/docs/decisions.md @@ -244,8 +244,8 @@ carry both rules and both scopes anyway, and tell them apart at every step. ## A hold set makes its draw maps on the first read -Every render and every draw group starts from an empty hold, since goal 2 prices a reader -meeting two spellings of one empty set. Making the maps where the set is declared kept a +Every render starts from an empty hold set, its draw groups included, since goal 2 prices +a reader meeting two spellings of one empty set. Making the maps where the set is declared kept a record's on its frame's stack, but a `Fake`'s set lives on the `Generator`, so there it cost the cheapest render two heap allocations and 240→390 ns, measured 2026-09-28. Lazily, a render reading a reference path pays those two allocations, a record or struct