From 407376a6facd600d08aaef263abdab973c86cd9c Mon Sep 17 00:00:00 2001 From: ben Date: Sun, 20 Mar 2016 10:59:48 -0400 Subject: [PATCH] [icfp] typos, redundancy --- icfp-2016/implementation.scrbl | 4 ++-- icfp-2016/usage.scrbl | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/icfp-2016/implementation.scrbl b/icfp-2016/implementation.scrbl index 58c3ada..ea6ba06 100644 --- a/icfp-2016/implementation.scrbl +++ b/icfp-2016/implementation.scrbl @@ -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. diff --git a/icfp-2016/usage.scrbl b/icfp-2016/usage.scrbl index 0022a48..4c0aefd 100644 --- a/icfp-2016/usage.scrbl +++ b/icfp-2016/usage.scrbl @@ -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. @; =============================================================================