about summary refs log tree commit diff stats
path: root/subx/029transforms.cc
diff options
context:
space:
mode:
authorKartik Agaram <vc@akkartik.com>2018-09-26 10:35:06 -0700
committerKartik Agaram <vc@akkartik.com>2018-09-26 10:35:06 -0700
commitd7d0546f22893e8cbe84a734e2f349af62af634b (patch)
tree935d2831fd73c6773662a2a9dea2ae81393e5ad1 /subx/029transforms.cc
parentbc3e572acd4bfb3556c2361c7c6559380eacda0a (diff)
downloadmu-d7d0546f22893e8cbe84a734e2f349af62af634b.tar.gz
4519
Diffstat (limited to 'subx/029transforms.cc')
-rw-r--r--subx/029transforms.cc6
1 files changed, 3 insertions, 3 deletions
diff --git a/subx/029transforms.cc b/subx/029transforms.cc
index 9546ea91..a6e12502 100644
--- a/subx/029transforms.cc
+++ b/subx/029transforms.cc
@@ -50,10 +50,10 @@
 //:   representation by showing how it's transformed to the level below. To
 //:   make such exceptions more obvious checks usually won't be first-class
 //:   transforms; instead code that keeps the program unmodified will run
-//:   within transforms before they mutate the program.
+//:   within transforms before they mutate the program. As an example:
 //:
-//:     Level l transforms programs
-//:     Level l+1 inserts checks to run *before* the transform of level l runs
+//:     Layer l introduces a transform
+//:     Layer l+1 adds precondition checks for the transform
 //:
 //: This may all seem abstract, but will hopefully make sense over time. The
 //: goals are basically to always have a working program after any layer, to