fix guide typos

Closes PR 11700
 Merge to 5.1
This commit is contained in:
Matthew Flatt 2011-02-03 06:30:10 -07:00
parent 16eb172e5a
commit 08cc4dffb2
2 changed files with 5 additions and 5 deletions

View File

@ -84,9 +84,9 @@ variables} that are bound in the result expressions:
(match '(1 2)
[(list x) (+ x 1)]
[(list x y) (+ x y)])
(match (make-hat 23 'bowler)
[(struct shoe (sz col)) sz]
[(struct hat (sz stl)) sz])
(match (hat 23 'bowler)
[(shoe sz col) sz]
[(hat sz stl) sz])
]
An ellipsis, written @litchar{...}, act like a Kleene star within a

View File

@ -64,10 +64,10 @@ The module system aids optimization by helping to ensure that
identifiers have the usual bindings. That is, the @racket[+] provided
by @racketmodname[racket/base] can be recognized by the compiler and
inlined, which is especially important for @tech{JIT}-compiled code.
In contrast, in a traditional interactive Racket system, the top-level
In contrast, in a traditional interactive Scheme system, the top-level
@racket[+] binding might be redefined, so the compiler cannot assume a
fixed @racket[+] binding (unless special flags or declarations
act as a poor-man's module system to indicate otherwise).
are used to compensate for the lack of a module system).
Even in the top-level environment, importing with @racket[require]
enables some inlining optimizations. Although a @racket[+] definition