more edits from Carcaldi and a few to expose allocation in the Lambda chapter

Author: jsiek

book.bib

@@ -964,7 +964,7 @@ @inproceedings{Keep:2012ab
 
 @article{Church:1932aa,
   author =        {Church, Alonzo},
-  journal =       {Annals of Mathematics},
+  journal =       {Ann. Math.},
   number =        {2},
   pages =         {346--366},
   publisher =     {Annals of Mathematics},

book.tex

@@ -179,7 +179,7 @@
 {\if\edition\pythonEd
 Library of Congress Cataloging-in-Publication Data\\
 \ \\
-Names: Jeremy G. Siek.  \\
+Names: Siek, Jeremy, author.  \\
 Title: Essentials of compilation : an incremental approach in Python / Jeremy G. Siek.  \\
 Description: Cambridge, Massachusetts : The MIT Press, [2023] | Includes 
    bibliographical references and index. \\
@@ -2536,7 +2536,7 @@ \section{The \LangXInt{} Assembly Language}
 value. There are 16 general-purpose registers in the computer; their
 names are given in figure~\ref{fig:x86-int-concrete}.  A register is
 written with a percent sign, \key{\%}, followed by its name,
-for example \key{\%rax}.
+for example, \key{\%rax}.
 
 An immediate value is written using the notation \key{\$}$n$ where $n$
 is an integer.
@@ -7870,8 +7870,9 @@ \section{The \LangIf{} Language}
 Figure~\ref{fig:interp-Lif} shows the definition of the interpreter
 for \LangIf{}, which inherits from the interpreter for \LangVar{}
 (figure~\ref{fig:interp-Lvar}). The constants \TRUE{} and \FALSE{}
-evaluate to the corresponding Boolean values, which is
-inherited from the interpreter for \LangInt{} (figure~\ref{fig:interp-Lint-class}).
+evaluate to the corresponding Boolean values, behavior that is
+inherited from the interpreter for \LangInt{}
+(figure~\ref{fig:interp-Lint-class}).
 The conditional expression $\CIF{e_1}{e_2}{\itm{e_3}}$ evaluates
 expression $e_1$ and then either evaluates $e_2$ or $e_3$, depending
 on whether $e_1$ produced \TRUE{} or \FALSE{}. The logical operations
@@ -10835,7 +10836,7 @@ \subsection{Remove Jumps}
 \section{Further Reading}
 \label{sec:cond-further-reading}
 
-The algorithm for the \code{explicate\_control} pass is based on the
+The algorithm for \code{explicate\_control} is based on the
 \code{expose-basic-blocks} pass in the course notes of
 \citet{Dybvig:2010aa}.
 %
@@ -12911,7 +12912,7 @@ \section{Expose Allocation}
 the \code{expose\_allocation} pass before
 \code{remove\_complex\_operands} because it generates code that
 contains complex operands. However, with some care it can also be
-placed before \code{remove\_complex\_operands} which would simplify
+placed before \code{remove\_complex\_operands}, which would simplify
 tuple creation by removing the need to assign the initializing
 expressions to temporary variables (see below).
 
@@ -14289,7 +14290,7 @@ \section{Challenge: Arrays}
 {\if\edition\pythonEd\pythonColor
 %
 The type checker for \LangArray{} is defined in
-figure~\ref{fig:type-check-Lvecof} and
+figures~\ref{fig:type-check-Lvecof} and
 \ref{fig:type-check-Lvecof-part2}. The result type of a list literal
 is \code{list[T]}, where \code{T} is the type of the initializing
 expressions.  The type checking of the \code{len} function and the
@@ -14586,7 +14587,7 @@ \subsection{Overload Resolution}
 Translate the reading of an array element to
 \racket{\code{vectorof-ref}}\python{\code{array\_load}}
 and the writing of an array element to
-\racket{\code{vectorof-set!}}\python{\code{array\_store}}
+\racket{\code{vectorof-set!}}\python{\code{array\_store}}.
 Translate calls to \racket{\code{vector-length}}\python{\code{len}}
 into \racket{\code{vectorof-length}}\python{\code{array\_len}}.
 When these operators are applied to tuples, leave them as is.
@@ -15205,10 +15206,10 @@ \section{The \LangFun{} Language}
   \code{env} with the parameters of the function. We then type check
   the body of the function and obtain the actual return type
   \code{rt}, which is either the type of the expression in a
-  \code{return} statement, or the \code{VoidType} if control reaches
+  \code{return} statement or the \code{VoidType} if control reaches
   the end of the function without a \code{return} statement.  (If
   there are multiple \code{return} statements, the types of their
-  expressions must agree.) Finally we check that the actual return
+  expressions must agree.) Finally, we check that the actual return
   type \code{rt} is equal to the declared return type \code{returns}.}
 %
 To check a function \racket{application}\python{call}, we match
@@ -17888,12 +17889,16 @@ \subsection{An Example Translation}
 \section{Expose Allocation}
 \label{sec:expose-allocation-r5}
 
-Compile the $\CLOSURE{\itm{arity}}{\Exp^{*}}$ form into code
-that allocates and initializes a tuple, similar to the translation of
-the tuple creation in section~\ref{sec:expose-allocation}.
-The only difference is replacing the use of
-\ALLOC{\itm{len}}{\itm{type}} with
-\ALLOCCLOS{\itm{len}}{\itm{type}}{\itm{arity}}.
+Compile the $\CLOSURE{\itm{arity}}{\Exp^{*}}$ form into code that
+allocates and initializes a tuple, similar to the translation of the
+tuple creation in section~\ref{sec:expose-allocation}.  The main
+difference is replacing the use of \ALLOC{\itm{len}}{\itm{type}} with
+\ALLOCCLOS{\itm{len}}{\itm{type}}{\itm{arity}}.  The result type of
+the translation of $\CLOSURE{\itm{arity}}{\Exp^{*}}$ should be a tuple
+type, but only a single element tuple type. The types of the tuple
+elements that correspond to the free variables of the closure should
+not appear in the tuple type. The new AST class \code{UncheckedCast}
+can be used to adjust the result type.
 
 
 \section{Explicate Control and \LangCLam{}}
@@ -17929,6 +17934,7 @@ \section{Explicate Control and \LangCLam{}}
 \Exp &::=& \key{Uninitialized}\LP \Type \RP
       \MID \key{AllocateClosure}\LP\itm{len},\Type, \itm{arity}\RP \\
       &\MID& \ARITY{\Atm}
+      \MID \key{UncheckedCast}\LP\Exp,\Type\RP
 \end{array}
 }