Okay, this seems complex. I think I'll put that off until another day
as well. Here's where I got bogged down. When I run this program:
#lang racket/base
(define (f x)
(+ x x
x x
x x
x x
x x))
the answer should probably be "one uncovered expression" but the data
I have to work with is this:
(#f #(struct:srcloc #(struct:object:...ivate/get-extend.rkt:134:12
...) #f #f 38 1))
(#t #(struct:srcloc #(struct:object:...ivate/get-extend.rkt:134:12
...) #f #f 28 1))
(#f #(struct:srcloc #(struct:object:...ivate/get-extend.rkt:134:12
...) #f #f 79 1))
(#f #(struct:srcloc #(struct:object:...ivate/get-extend.rkt:134:12
...) #f #f 36 1))
(#f #(struct:srcloc #(struct:object:...ivate/get-extend.rkt:134:12
...) #f #f 47 1))
(#f #(struct:srcloc #(struct:object:...ivate/get-extend.rkt:134:12
...) #f #f 95 1))
(#f #(struct:srcloc #(struct:object:...ivate/get-extend.rkt:134:12
...) #f #f 86 1))
(#f #(struct:srcloc #(struct:object:...ivate/get-extend.rkt:134:12
...) #f #f 63 1))
(#f #(struct:srcloc #(struct:object:...ivate/get-extend.rkt:134:12
...) #f #f 70 1))
(#f #(struct:srcloc #(struct:object:...ivate/get-extend.rkt:134:12
...) #f #f 54 1))
(#f #(struct:srcloc #(struct:object:...ivate/get-extend.rkt:134:12
...) #f #f 111 1))
(#f #(struct:srcloc #(struct:object:...ivate/get-extend.rkt:134:12
...) #f #f 35 78))
(#f #(struct:srcloc #(struct:object:...ivate/get-extend.rkt:134:12
...) #f #f 102 1))
(#t #(struct:srcloc #(struct:object:...ivate/get-extend.rkt:134:12
...) #f #f 19 95))
(#t #(struct:srcloc #(struct:object:...ivate/get-extend.rkt:134:12
...) #f #f 1 122))
Anyway, I pushed something that matches the predicate that's already
implemented, reflecting it into the GUI. It probably doesn't bounce as
much as Eli & John hope, but maybe it is okay for now.
Robby
On Tue, Feb 16, 2016 at 8:22 AM, Robby Findler
<ro...@eecs.northwestern.edu> wrote:
> I'm sorry: that was a bit too telegraphic. I'm asking if the program
> below counts as one or some other number of uncovered regions. And
> things like that. I'm going to go with 1 here but another approach
> would be to show a percentage covered based on characters or
> something.
>
> Robby
>
> #lang racket
> (define-syntax (m stx)
> (syntax-case stx ()
> [(_ a b c)
> #`(void (λ () #,(datum->syntax #'here '(void) stx))
> #,(datum->syntax #'here '(void) #'b))]))
>
> (m abcdef
> ghijkl
> mnopqr)
>
> On Tue, Feb 16, 2016 at 7:59 AM, Robby Findler
> <ro...@eecs.northwestern.edu> wrote:
>> How do you do this count? (what algorithm?)
>>
>> Robby
>>
>> On Tue, Feb 16, 2016 at 6:56 AM, Greg Hendershott
>> <greghendersh...@gmail.com> wrote:
>>> FWIW when you run tests with coverage in racket-mode (C-u C-c C-t)
>>> displays in the echo area either "Coverge complete" or "Missing
>>> coverage in N places". In the latter case, point moves to the first
>>> place. All such places are colored in red.
>>>
>>> One thing racket-mode should probably also do is have next-error to
>>> jump to later spots (if any). However I figured people would add
>>> coverage one spot at a time, so it didn't seem super compelling.
>>>
>>>
>>> On Tue, Feb 16, 2016 at 6:21 AM, Eli Barzilay <e...@barzilay.org> wrote:
>>>> Re leaving the coverage colors: for the purpose of my class that would
>>>> do fine, but for actual use, the lack of full coverage indication means
>>>> that you'll need to scroll through the text to find out if you have it
>>>> or not...
>>>>
>>>> So something like a status bar message would be better, either with
>>>> leaving the coverage colors or not. Even better if it "jumps up" as
>>>> John said, so that it draws attention to it.
>>>>
>>>> --
>>>> ((x=>x(x))(x=>x(x))) Eli Barzilay:
>>>> http://barzilay.org/ Maze is Life!
>>>>
>>>> --
>>>> 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.
