Racket module boundaries and contract enforcement: retroactive wrapping of unannotated exports
In Racket, the contract system is designed to enforce runtime checks on function inputs and outputs across module boundaries. A common integration scenario arises when one module exports a function without a contract-out annotation, and a downstream module wishes to enforce a stricter contract on that import without modifying the upstream source. The standar
racket