Okay, I've pushed a change that adds #:pre/name and #:post/name to ->i. Let me know how it works for you.
Robby On Tue, Feb 22, 2011 at 6:17 PM, Eric Dobson <endob...@cs.brown.edu> wrote: > I was thinking a string. I just want the ability to specify which > invariant that the precondition was checking was broken. > > -Eric > > On Tue, Feb 22, 2011 at 7:13 PM, Robby Findler > <ro...@eecs.northwestern.edu> wrote: >> Not currently, no. What kind of information did you have in mind? >> >> Robby >> >> On Tue, Feb 22, 2011 at 6:05 PM, Eric Dobson <endob...@cs.brown.edu> wrote: >>> I am adding contracts to one of my libraries using the ->i combinator >>> and using the pre-condition expression. The problem I have is that if >>> I return false, the contract library just tells me that the >>> precondition failed. Is there any mechanism to attach more information >>> so that I can explain why the precondition failed? >>> >>> -Eric >>> _________________________________________________ >>> For list-related administrative tasks: >>> http://lists.racket-lang.org/listinfo/users >>> >> > _________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/users
