|(provide/contract p/c-item )|
The provide/contract form treats modules as units of blame. The module that defines the provided variable is expected to meet the positive (co-variant) positions of the contract. Each module that imports the provided variable must obey the negative (contra-variant) positions of the contract.
Only uses of the contracted variable outside the module are checked. Inside the module, no contract checking occurs.
The struct form of a provide/contract clause provides a structure definition, and each field has a contract that dictates the contents of the fields. The struct definition must come before the provide clause in the module’s body. If the struct has a parent, the second struct form (above) must be used, with the first name referring to the struct itself and the second name referring to the parent struct. Unlike define-struct, however, all of the fields (and their contracts) must be listed. The contract on the fields that the sub-struct shares with its parent are only used in the contract for the sub-struct’s maker, and the selector or mutators for the super-struct are not provided.
|(with-contract blame-id (wc-export ) free-var-list body )|
The blame-id is used for the positive positions of contracts paired with exported ids. Contracts broken within the with-contract body will use the blame-id for their negative position.
If a free-var-list is given, then any uses of the free variables inside the body will be protected with contracts that blame the context of the with-contract form for the positive positions and the with-contract form for the negative ones.
|(define/contract id contract-expr free-var-list init-value-expr)|
|(define/contract (head args) contract-expr free-var-list body )|
The define/contract form treats the individual definition as a contract region. The definition itself is responsible for positive (co-variant) positions of the contract and references to id outside of the definition must meet the negative positions of the contract. Since the contract boundary is between the definition and the surrounding context, references to id inside the define/contract form are not checked.
If a free-var-list is given, then any uses of the free variables inside the body will be protected with contracts that blame the context of the define/contract form for the positive positions and the define/contract form for the negative ones.
The define-struct/contract form only allows a subset of the struct-option keywords: #:mutable, #:transparent, #:auto-value, #:omit-define-syntaxes, and #:omit-define-values.
The contract expression adds the contract specified by contract-expr to the value produced by to-protect-expr. The result of a contract expression is the result of the to-protect-expr expression, but with the contract specified by contract-expr enforced on to-protect-expr.
The values of positive-blame-expr and negative-blame-expr must be symbols indicating how to assign blame for positive and negative positions of the contract specified by contract-expr.
a list of two elements: srcloc struct and either a string or #f. The srcloc struct inidates where the contract was assumed. Its source field should be a syntax object, and module-path-index-resolve is called on it to extract the path of syntax object.
If the second element of the list is not #f, it is used as the name of the identifier whose contract was assumed.
a syntax object specifying the source location of the location where the contract was assumed. If the syntax object wraps a symbol, the symbol is used as the name of the primitive whose contract was assumed.
If absent, it defaults to the source location of the contract expression with no identifying name.
The second form above is not recommended, because mzscheme strips source location information from compiled files.