[icfp] typos, redundancy

This commit is contained in:
ben 2016-03-20 10:59:48 -04:00
parent 688a3c16c3
commit 407376a6fa
2 changed files with 3 additions and 3 deletions

View File

@ -484,7 +484,7 @@ Perhaps it goes without saying, but having macros that respect lexical scope
is important for a good user and developer experience.
Along the same lines, the ability to propogate source code locations in
elaborations lets us report syntax errors in terms of the programmer's
source code rather than locations inside our library.
code rather than locations inside our library.
Even though we may implement complex transformations, errors can always be
traced to a source code line number.
traced to a line number in the source.

View File

@ -328,7 +328,7 @@ Taken alone, this re-implementation of constant folding in an earlier compiler
stage is not very exciting.
But since folded expressions propagate their result upwards to arbitrary
analyses, we can combine these elaborations with a size-aware vector library to
guard against index errors access at computed locations.
guard against index errors at computed locations.
@; =============================================================================