[racket-users] Issue with the catalog (package removed and re-added does not appear)

Hi all! I tried adding a "version exception" earlier, which partially failed (rendering that package unusable on version in question, with the error "cannot use empty checksum for Git repostory package source"). As a last ressort, I tried removing the package and re-adding it, but now

Re: [racket-users] ->i applies contract projections multiple times?

On Fri, Dec 16, 2016 at 12:20 PM, Alexis King wrote: >> On Dec 16, 2016, at 9:53 AM, Robby Findler >> wrote: >> >> Picky would never assign blame to m1. The places where m1 would be >> blamed would instead fall on, I think, m2. > > Ahh, I see.

Re: [racket-users] ->i applies contract projections multiple times?

> On Dec 16, 2016, at 9:53 AM, Robby Findler > wrote: > > Picky would never assign blame to m1. The places where m1 would be > blamed would instead fall on, I think, m2. Ahh, I see. I was confused because I wasn’t paying enough attention to the blame information in

Re: [racket-users] Re: Operations that create objects

Two examples: #lang racket (define (create-function-that-show-number n) (display "*") (lambda () (displayln n))) ;Create the function (define f7 (create-function-that-show-number 7)) ;Use it (displayln "Hello") (f7) (displayln "World!") ;--- ;Something more complex

Re: [racket-users] ->i applies contract projections multiple times?

On Fri, Dec 16, 2016 at 11:49 AM, Alexis King wrote: >> On Dec 15, 2016, at 3:16 PM, Robby Findler >> wrote: >> >> But if you want to know more about how they could be different, you >> might want to consider this example from section 1 of the

Re: [racket-users] ->i applies contract projections multiple times?

> On Dec 15, 2016, at 3:16 PM, Robby Findler > wrote: > > But if you want to know more about how they could be different, you > might want to consider this example from section 1 of the paper. It > will (randomly) assign blame to any of the three submodules. Hmm.

Re: [racket-users] Re: Operations that create objects

The outer function must return the inner function (or otherwise make it reachable, perhaps inside some data structure). For example: > (define (make-counter init) (define (counter) (set! init (add1 init)) init) (displayln "Making a counter!") counter) > (define

Re: [racket-users] Re: Operations that create objects

Thank you so much. This is extremely helpful and instructive. One thing I don't understand: how do you call or access an inner function after its outer function has completed? On Fri, Dec 16, 2016 at 5:41 AM, George Neuner wrote: > On Thu, 15 Dec 2016 06:03:54 -0800