suzanne.soy/trivial
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[rebuttal] propAgate

Browse Source
This commit is contained in:
Ben Greenman 2016-05-03 05:57:35 -04:00
parent 7a933236b5
commit 522b407b53
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
icfp-2016/implementation.scrbl
View File

@ -358,7 +358,7 @@ This ``lazy'' sort of evaluation is normally useful because it lets macro
the syntax trees of expanded code.
Our elaborations, however, are most effective when value information is
propogated bottom up from macro-free syntactic values through other combinators.
propagated bottom up from macro-free syntactic values through other combinators.
This requires depth-first macro expansion; for instance, in the first argument
of the @racket[vector-ref] elaboration defined in @Secref{sec:impl-elab}.
Fortunately, we always know which positions to expand depth-first and
@ -482,7 +482,7 @@ We also have functions like @racket[+] available at whatever stage of
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
Along the same lines, the ability to propagate source code locations in
elaborations lets us report syntax errors in terms of the programmer's
code rather than locations inside our library.
Even though we may implement complex transformations, errors can always be