minor guide corrections
on parts that Eli asked me to check
This commit is contained in:
parent
1e4186098e
commit
4eb0d3dcac
|
@ -8,9 +8,9 @@ same syntactic keyword @racket[let] as for local binding, but an
|
|||
identifier after the @racket[let] (instead of an immediate open
|
||||
parenthesis) triggers a different parsing.
|
||||
|
||||
@racketblock[
|
||||
(let _proc-id ([_arg-id _init-expr] ...)
|
||||
_body ...+)
|
||||
@specform[
|
||||
(let proc-id ([arg-id init-expr] ...)
|
||||
body ...+)
|
||||
]
|
||||
|
||||
A named @racket[let] form is equivalent to
|
||||
|
|
|
@ -60,7 +60,7 @@ with a @deftech{dye pack}. When a syntax object is armed, then
|
|||
@racket[syntax-e] taints any syntax object in its result. Similarly,
|
||||
@racket[datum->syntax] taints its result when its first argument is
|
||||
armed. Finally, if any part of a quoted syntax object is armed, then
|
||||
the corresponding part taints the resulting syntax constant.
|
||||
the corresponding part is tainted in the resulting syntax constant.
|
||||
|
||||
Of course, the macro expander itself must be able to @deftech{disarm}
|
||||
a taint on a syntax object, so that it can further expand an
|
||||
|
|
Loading…
Reference in New Issue
Block a user