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

fix docs again on struct in racket/signature

Browse Source 
The repair of 7bfe2eadab wasn't right; the `struct` form is treated
correctly in `define-signature`, but not in `racket/signature`.
This commit is contained in:
Matthew Flatt 2015-02-08 06:49:53 -07:00
parent 2ada651dd3
commit fe68c9ab81
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
pkgs/racket-doc/scribblings/reference/units.scrbl
View File

@ -222,7 +222,7 @@ of bindings for import or export:
specified by @racket[sig-spec].}
@item{Each @racket[(struct id (field ...) struct-option ...)] adds
all of the identifiers that would be bound by @racket[(define-struct id
all of the identifiers that would be bound by @racket[(struct id
(field ...) field-option ...)], where the extra option
@racket[#:omit-constructor] omits the constructor identifier.}
@ -782,7 +782,6 @@ Unlike the body of a @racketmodname[racket/unit] module, a
@racket[require] in a @racketmodname[racket/signature] module must be
a literal use of @racket[require].
The resulting signature is exported as
@racket[_base]@racketidfont["^"], where @racket[_base] is derived from
the enclosing module's name (i.e., its symbolic name, or its path
@ -791,6 +790,11 @@ without the directory and file suffix). If the module name ends in
name before @racketidfont{-sig}. Otherwise, the module name serves as
@racket[_base].
A @racket[struct] form as a @racket[sig-spec] is consistent with the
definitions introduced by @racket[define-struct], as opposed to
definitions introduced @racket[struct]. (That behavior was originally
a bug, but it is preserved for compatibility.)
@; ----------------------------------------------------------------------
@section{Transformer Helpers}