[racket-dev] [racket] Implementing contracts for async channels

This seemed okay, but just a quick read of the code. But did I miss
the test cases? (I just followed the link upthread -- sorry if I need
to look somewhere else too.)

Robby


On Mon, Jan 19, 2015 at 3:15 PM, Alexis King <lexi.lambda at gmail.com> wrote:
> Any update on this? If there’s anything that still needs to be changed, let me know—otherwise, I’ll patiently wait for the process to run its course. Just checking in.
>
>> On Jan 16, 2015, at 10:15, Alexis King <lexi.lambda at gmail.com> wrote:
>>
>> Ah, that makes sense, fixed.
>>
>>> On Jan 16, 2015, at 05:37, Robby Findler <robby at eecs.northwestern.edu> wrote:
>>>
>>> One comment. The contract combinators are curried so that you can do
>>> work on the partial applications. So don't write this:
>>>
>>> (define ((((ho-val-first-projection
>>> impersonate/chaperone-async-channel) ctc) blame) val)
>>>
>>> instead try to do some work earlier, when you first can. (The most
>>> important thing is to minimize the work done after you get the 'val'
>>> argument.)
>>>
>>> Robby
>>
>
>
> _________________________
>   Racket Developers list:
>   http://lists.racket-lang.org/dev