updated docs for struct-type-contract/c
This commit is contained in:
parent
59a85b3eb2
commit
5a10ef7550
|
@ -16,34 +16,57 @@
|
|||
|
||||
Produces a contract for struct type properties. When the contract is
|
||||
applied to a struct type property, it produces a wrapped struct type
|
||||
property. When the wrapped struct type property is used to create a
|
||||
new struct type (via @racket[struct], @racket[make-struct-type], etc),
|
||||
it applies @racket[value-contract] to the value associated with the
|
||||
property.
|
||||
property that applies @racket[value-contract] to the value associated
|
||||
with the property when used to create a new struct type (via
|
||||
@racket[struct], @racket[make-struct-type], etc).
|
||||
|
||||
The contract has no effect on the struct type property accessor.
|
||||
The struct type property's accessor function is not affected; it must
|
||||
be protected separately.
|
||||
|
||||
@examples[#:eval the-eval
|
||||
(define-values (prop prop? prop-ref)
|
||||
(make-struct-type-property 'prop))
|
||||
(module propmod racket
|
||||
(require racket/contract
|
||||
unstable/prop-contract)
|
||||
(define-values (prop prop? prop-ref)
|
||||
(make-struct-type-property 'prop))
|
||||
(define (prop-app x v)
|
||||
(((prop-ref x) x) v))
|
||||
(provide/contract
|
||||
[prop? (-> any/c boolean?)]
|
||||
[prop (struct-type-property/c
|
||||
(-> prop? (-> number? boolean?)))]
|
||||
[prop-app (-> prop? number? boolean?)])
|
||||
(provide prop-ref))
|
||||
|
||||
(define/contract wrapped
|
||||
(struct-type-property/c (-> any/c (-> number? number?)))
|
||||
prop)
|
||||
(module structmod racket
|
||||
(require 'propmod)
|
||||
(struct s (f) #:property prop (lambda (s) (s-f s)))
|
||||
(provide (struct-out s)))
|
||||
|
||||
(struct s (f)
|
||||
#:property wrapped (lambda (s) (s-f s)))
|
||||
(require 'propmod 'structmod)
|
||||
(define s1 (s even?))
|
||||
(prop-app s1 5)
|
||||
(prop-app s1 'apple)
|
||||
|
||||
(define (get-f s) ((prop-ref s) s))
|
||||
(define s2 (s "not a fun"))
|
||||
(prop-app s2 5)
|
||||
|
||||
(define s1 (s add1))
|
||||
((get-f s1) 5)
|
||||
((get-f s1) 'apple)
|
||||
(define s3 (s list))
|
||||
(prop-app s3 5)
|
||||
|
||||
(define s2 (s (lambda (n) (if (zero? n) 'zero 'nonzero))))
|
||||
((get-f s2) 5)
|
||||
((get-f s2) 'apple)
|
||||
((prop-ref s3) 'apple)
|
||||
]
|
||||
The first contract error above is a simple function contract violation
|
||||
on @racket[prop-app]. The second and third contract errors above blame
|
||||
the @racketidfont{structmod} module, because it accepted the struct type
|
||||
property contract. To avoid blame, @racketidfont{structmod}
|
||||
should have placed a contract on @racket[s]. The final contract error,
|
||||
involving @racket[s3], blames @racketidfont{propmod} because the struct
|
||||
type property contract obliges @racketidfont{propmod} to make sure the
|
||||
property's value is not misused, but @racketidfont{propmod} allows
|
||||
direct access to the property value via @racket[prop-ref]. To
|
||||
avoid blame, @racketidfont{propmod} should remove the export of
|
||||
@racket[prop-ref] or protect it with a contract.
|
||||
}
|
||||
|
||||
@close-eval[the-eval]
|
||||
|
|
Loading…
Reference in New Issue
Block a user