From 2d51b64758db57e7d549639d12af35d03a0bd3d8 Mon Sep 17 00:00:00 2001
From: Cliff Click <cliffc@acm.org>
Date: Tue, 29 Sep 2026 17:10:17 -0700
Subject: Forward port lazy mem eval to ch18

---
 chapter17/README.md | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

(limited to 'chapter17/README.md')

diff --git a/chapter17/README.md b/chapter17/README.md
index cdbca21b..a3a2d992 100644
--- a/chapter17/README.md
+++ b/chapter17/README.md
@@ -165,3 +165,18 @@ for( int i=0; i<ary#; i++ )
     return i;
 return -1;
 ```
+
+## Memory effects
+
+The lazy memory representation from [Chapter 10b](../chapter10b/README.md) and
+constructor layout from [Chapter 16](../chapter16/README.md#memory-through-constructors)
+continue here. ScopeNode tracks one `$mem` binding. Field and array writes,
+including increments, update their alias in a MemMerge. Branches, conditional
+expressions, and loops merge whole memory with BulkMemPhi; MemPhis are discovered
+as field uses require them.
+
+Readonly references retain their deep immutability when Loads fold through
+Stores or allocations. Forward reference types still resolve lazily. Phi
+factoring uses the same one-step Load safety check. Allocation memory remains
+shared across the struct's aliases, so the sole-use Store-to-New check may
+leave a Load that separate memory projections allowed to fold.
-- 
cgit v1.2.3