If I'm following correctly, I think that's what I was trying to do, but I'm unclear how to give `make-deserialize-info` a variant of `make-adder` that has a contract. The initial example with `define/contract` was the closest I've come: it at least reported violations in terms of `make-adder` rather than `+`, but (as I now understand) it blamed the `server` module for all violations.
-Philip On Sun, Jul 23, 2017 at 9:27 PM, Matthew Flatt <mfl...@cs.utah.edu> wrote: > The original example had an explicit deserializer: > > At Sun, 23 Jul 2017 19:54:43 -0500, Philip McGrath wrote: > > (define deserialize-info:adder-v0 > > (make-deserialize-info make-adder > > (λ () (error 'adder > > "can't have cycles")))) > > You're constructing the deserializer with `make-adder` --- the variant > from inside the `server` module, so it doesn't have a contract. > > I think this is where you want to draw a new boundary by giving > `make-deserialize-info` a variant of `make-adder` that has a contract. > > -- > You received this message because you are subscribed to the Google Groups > "Racket Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to racket-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
