Fix some typos
This commit is contained in:
parent
1d5f34f623
commit
ab025cbf47
|
@ -125,7 +125,7 @@ argument. More often, the namespace used by a dynamic operation is the
|
|||
@margin-note{See @secref["parameterize"] for an introduction to
|
||||
parameters.}
|
||||
|
||||
When @racket[eval] is used in a @tech{REPL}, the current is the one
|
||||
When @racket[eval] is used in a @tech{REPL}, the current namespace is the one
|
||||
that the @tech{REPL} uses for evaluating expressions. That's why the
|
||||
following interaction successfully accesses @racket[x] via
|
||||
@racket[eval]:
|
||||
|
@ -178,7 +178,7 @@ way to reflect a module into a @tech{namespace}.
|
|||
|
||||
The @racket[module->namespace] function takes a quoted @tech{module
|
||||
path} and produces a namespace for evaluating expressions and
|
||||
definitions as if they appears in the @racket[module] body:
|
||||
definitions as if they appeared in the @racket[module] body:
|
||||
|
||||
@interaction[
|
||||
(module m racket/base
|
||||
|
|
|
@ -117,7 +117,7 @@ Racket programmers prefer to avoid side-effects, so a definition usually
|
|||
has just one expression in its body. It's
|
||||
important, though, to understand that multiple expressions are allowed
|
||||
in a definition body, because it explains why the following
|
||||
@racket[nobake] function simply returns its argument:
|
||||
@racket[nobake] function fails to return its argument:
|
||||
|
||||
@def+int[
|
||||
#:eval ex-eval
|
||||
|
|
|
@ -11,7 +11,7 @@ update of its elements.
|
|||
|
||||
A vector prints similar to a list---as a parenthesized sequence of its
|
||||
elements---but a vector is prefixed with @litchar{#} after
|
||||
@litchar{'}, or it uses @schemeresult[vector] of one of its elements
|
||||
@litchar{'}, or it uses @schemeresult[vector] if one of its elements
|
||||
cannot be expressed with @racket[quote].
|
||||
|
||||
For a vector as an expression, an optional length can be
|
||||
|
@ -35,7 +35,7 @@ Vector can be converted to lists and vice versa via
|
|||
@racket[list->vector] and @racket[vector->list]; such conversions are
|
||||
particularly useful in combination with predefined procedures on
|
||||
lists. When allocating extra lists seems too expensive, consider
|
||||
using looping forms like @racket[fold-for], which recognize vectors as
|
||||
using looping forms like @racket[for/fold], which recognize vectors as
|
||||
well as lists.
|
||||
|
||||
@examples[
|
||||
|
|
Loading…
Reference in New Issue
Block a user