Many thanks to both of you for the explanation and examples. I admit I’ve seen that paper before, but I haven’t really taken the time to understand it. I haven’t spent the effort to understand all the notation being used, so much of the paper is pretty opaque to me. Maybe once I get some time I’ll sift through it more carefully, but in the meantime, Scott’s example helps a lot to demonstrate what indy dependent contracts actually do.
However, from a practical implementation perspective, I’m still a little confused about why the contract needs to be applied twice. Given that Racket uses the +indy semantics, it seems like the blame provided is identical for both cases, so it seems like the contracts should only need to be applied once. For Scott’s example, the contract for the y argument needs to be applied such that if it is misused within the function body, then it blames foo, and if it is misused within the contract itself, it also blames foo. If ->i used the indy or -indy semantics (though admittedly I don’t get why the -indy semantics would ever be useful), I would understand why the contract would need to be applied twice, since the blame would be different. Given the way Racket handles things, though, I don’t really understand what I’m missing. -- 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.
