about summary refs log tree commit diff stats
diff options
context:
space:
mode:
authorKartik K. Agaram <vc@akkartik.com>2015-11-14 16:26:33 -0800
committerKartik K. Agaram <vc@akkartik.com>2015-11-14 16:26:33 -0800
commit687f871a932cefbb66b8eb189d312058f4e02a99 (patch)
tree8ed771e857ed304ad306a44e4d635c93f6b39e1b
parent417db83de5673d26c7b997d27dcbcffda949fcd0 (diff)
downloadmu-687f871a932cefbb66b8eb189d312058f4e02a99.tar.gz
2437
-rw-r--r--Readme.md7
1 files changed, 4 insertions, 3 deletions
diff --git a/Readme.md b/Readme.md
index ef6dd7a1..cda37208 100644
--- a/Readme.md
+++ b/Readme.md
@@ -135,9 +135,10 @@ Recipes can specify headers showing their expected ingredients and products,
 separated by `->` (unlike the `<-` in *calls*).
 
 Since mu is a low-level VM language, it provides extra control at the cost of
-verbosity. You have explicit control over stack frames to isolate your recipes
-(in a type-safe manner; more on that below), but you have to explicitly
-`load-ingredients` after you set up the stack.
+verbosity. Using `local-scope`, you have explicit control over stack frames to
+isolate your recipes (in a type-safe manner; more on that below). One
+consequence: you have to explicitly `load-ingredients` after you set up the
+stack.
 
 An alternative syntax is what the above example is converted to internally: