On Nov 20, 2010, at 8:19 PM, Sam Tobin-Hochstadt wrote: > There are a lot of things you could mean by "Typed Racket doesn't > preserve source locations". Some of them TR definitely preserves > source locations, and some are hard cases where TR tries but doesn't > always succeed. So I am also interested in an example.
Here's an example: #lang typed/racket (require typed/rackunit) (: f (Integer -> Boolean)) (define (f x) (odd? x)) (check-equal? (f 23421) #true) (check-equal? (f 33242) #false) (check-equal? (f 322) #true) Running this produces this output for me: -------------------- FAILURE name: check-equal? location: (unknown #f #f #f #f) expression: unknown params: (#f #t) actual: #f expected: #t -------------------- > So... which test case failed? No idea. Well, actually, in this case, I have *some* idea :). When it isn't a deliberately introduced bug, though, it's binary-search time to isolate which test case failed. I'm "rack"ing my brain to see whether this could be rackunit's fault, but I don't see how it could be.... Oh, unless the problem is that the "check-equal?" macro in typed/rackunit just needs some work... John
smime.p7s
Description: S/MIME cryptographic signature
_________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
