From d7d0546f22893e8cbe84a734e2f349af62af634b Mon Sep 17 00:00:00 2001 From: Kartik Agaram Date: Wed, 26 Sep 2018 10:35:06 -0700 Subject: 4519 --- subx/029transforms.cc | 6 +++--- 1 file 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 -- cgit 1.4.1-2-gfad0