summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCliff Click <cliffc@acm.org>2025-09-04 15:45:45 -0700
committerCliff Click <cliffc@acm.org>2025-09-04 15:45:45 -0700
commit89586c4679a02ea7210cce44e74d6cf2ad1ff6ef (patch)
tree6d69d19ba625bd5e574fabf625d064eb92dc25e7
parent3ccbe29489370a4f1dac6c4195c930577c9b713f (diff)
downloadSimple-89586c4679a02ea7210cce44e74d6cf2ad1ff6ef.tar.gz
Simple-89586c4679a02ea7210cce44e74d6cf2ad1ff6ef.zip
Update TypeAnalysis.md
-rw-r--r--TypeAnalysis.md5
1 files changed, 2 insertions, 3 deletions
diff --git a/TypeAnalysis.md b/TypeAnalysis.md
index 191e4287..96b023af 100644
--- a/TypeAnalysis.md
+++ b/TypeAnalysis.md
@@ -64,9 +64,8 @@ IR graph* or sometimes simply *nodes*.
Variations of constant propagation have a long history in compilers, and here I
am referring to the well understood [Monotone Analysis
Framework](http://janvitek.org/events/NEU/7580/papers/more-papers/1977-acta-kam-monotone.pdf); a quick google search finds plethora of courseworks on the topic. I assume the
-reader is familiar, and I also give a very brief overview here, because we are
-going to go deep down this rabbit hole.
-Constant propagation has long been used to discover interesting facts about program
+reader is familiar, and I also give a very brief overview here because we are
+going to go deep down this rabbit hole. Constant propagation has long been used to discover interesting facts about program
points, generally to further optimize a program. We are going to use it to
*type* our programs.