Re: [racket-dev] [plt] Push #23181: master branch updated

2011-08-08 Thread Casey Klein
On Mon, Aug 8, 2011 at 2:26 AM, Eli Barzilay e...@barzilay.org wrote: Two days ago, Casey Klein wrote: Oh, I see. I like that. How do you feel about using the same style for contracts? For example: (define-judgment-form nats     #:mode (sum I I O)     #:contract (sum n n n) Not a party

Re: [racket-dev] [racket] keyword args static checking and optimization

2011-08-08 Thread Matthew Flatt
[Moved to the dev list.] At Sat, 06 Aug 2011 07:25:00 -0400, Neil Van Dyke wrote: Feature request... I'd *really* like to see compile-time checking of keyword arguments whenever that is possible. If compiler knows what procedure will be called, and the procedure uses keyword args in the

Re: [racket-dev] [racket] keyword args static checking and optimization

2011-08-08 Thread Matthew Flatt
At Mon, 8 Aug 2011 10:12:36 -0500, Robby Findler wrote:   Another possibility is to redirect the `set!' on `f' to the   underlying `proc', and somehow make the optimized call to `core'   happen only when `proc' is never mutated. Due to the order of macro   expansion, whether `f' is mutated

Re: [racket-dev] [racket] keyword args static checking and optimization

2011-08-08 Thread Robby Findler
Ah, right. Rats. Robby On Mon, Aug 8, 2011 at 10:25 AM, Matthew Flatt mfl...@cs.utah.edu wrote: At Mon, 8 Aug 2011 10:12:36 -0500, Robby Findler wrote:   Another possibility is to redirect the `set!' on `f' to the   underlying `proc', and somehow make the optimized call to `core'   happen

[racket-dev] DrDr Feature Request

2011-08-08 Thread Vincent St-Amour
I love DrDr, but there's a small thing that annoys me about it. Some tests are prone to intermittent failures. For example, some benchmarks need to create a file, and several benchmarks share the same file, which leads to race conditions. Similarly, some DrRacket tests sometimes fail for focus

Re: [racket-dev] DrDr Feature Request

2011-08-08 Thread Robby Findler
I like the two-times-in-a-row thought. FWIW, please try to avoid race conditions of the second kind. I think the drracket test suites are special because they fail not-so-often and I don't actually know how to fix them. If either of those weren't true then I'd say they should just not run in

Re: [racket-dev] DrDr Feature Request

2011-08-08 Thread Robby Findler
PS: I'm also happy if this class of tests only emails the responsible person, and not the pusher. Robby On Mon, Aug 8, 2011 at 10:59 AM, Robby Findler ro...@eecs.northwestern.edu wrote: I like the two-times-in-a-row thought. FWIW, please try to avoid race conditions of the second kind. I

Re: [racket-dev] DrDr Feature Request

2011-08-08 Thread Vincent St-Amour
At Mon, 8 Aug 2011 10:59:24 -0500, Robby Findler wrote: FWIW, please try to avoid race conditions of the second kind. Some of these I can try to fix. But I don't think all intermittent failures fit in this category. I think the drracket test suites are special because they fail not-so-often

Re: [racket-dev] DrDr Feature Request

2011-08-08 Thread Robby Findler
On Mon, Aug 8, 2011 at 11:05 AM, Vincent St-Amour stamo...@ccs.neu.edu wrote: At Mon, 8 Aug 2011 10:59:24 -0500, Robby Findler wrote: FWIW, please try to avoid race conditions of the second kind. Some of these I can try to fix. But I don't think all intermittent failures fit in this

Re: [racket-dev] DrDr Feature Request

2011-08-08 Thread Vincent St-Amour
At Mon, 8 Aug 2011 11:06:30 -0500, Robby Findler wrote: On Mon, Aug 8, 2011 at 11:05 AM, Vincent St-Amour stamo...@ccs.neu.edu wrote: At Mon, 8 Aug 2011 10:59:24 -0500, Robby Findler wrote: FWIW, please try to avoid race conditions of the second kind. Some of these I can try to fix.

Re: [racket-dev] DrDr Feature Request

2011-08-08 Thread Jon Rafkind
Another request: could DrDr process the latest push first? Its a little annoying to get emails for tests that failed when the latest push fixes them but DrDr is so far behind. Is there any benefit to testing all the intermediate pushes? On 08/08/2011 09:56 AM, Vincent St-Amour wrote: I love

Re: [racket-dev] DrDr Feature Request

2011-08-08 Thread Robby Findler
This is a rare event (playing catchup like this) so I think it is probably best if we just let it catch up. Should be just a couple of more days (maybe a week) by my sketchy guesstimationizing. Robby On Mon, Aug 8, 2011 at 12:34 PM, Jon Rafkind rafk...@cs.utah.edu wrote: Another request: could

Re: [racket-dev] DrDr Feature Request

2011-08-08 Thread Jon Rafkind
Could DrDr say This build is not the latest or The latest push is 234234? On 08/08/2011 11:37 AM, Jay McCarthy wrote: It is useful to test all of them to find out when errors start. It doesn't do the newest first, because then the calculation of new issue wouldn't make any sense, because you

Re: [racket-dev] DrDr Feature Request

2011-08-08 Thread Jay McCarthy
Your wish is my command. On Mon, Aug 8, 2011 at 10:00 AM, Robby Findler ro...@eecs.northwestern.edu wrote: PS: I'm also happy if this class of tests only emails the responsible person, and not the pusher. Robby On Mon, Aug 8, 2011 at 10:59 AM, Robby Findler ro...@eecs.northwestern.edu

Re: [racket-dev] DrDr Feature Request

2011-08-08 Thread Jon Rafkind
I noticed this functionality just now.. thanks a lot! On 08/08/2011 12:38 PM, Jay McCarthy wrote: Your wish is my command. On Mon, Aug 8, 2011 at 10:00 AM, Robby Findler ro...@eecs.northwestern.edu wrote: PS: I'm also happy if this class of tests only emails the responsible person, and not