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

2015-01-19 Thread Alexis King
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 wrote: > > Ah, that makes sense, fixed. > >> On Jan 16, 2015, at 05:37, Robby Findle

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

2015-01-19 Thread Robby Findler
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 wrote: > Any update on this? If there’s anything that still needs to be chang

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

2015-01-19 Thread Alexis King
Yes, there are tests, and you can see them here . > On Jan 19, 2015, at 13:29, Robby Findler wrote: > > This seemed okay, but just a quick read of the code. But did I miss > the test cases? (I just followed th

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

2015-01-19 Thread Robby Findler
Ah: one other note. When you do something like this: ((contract (-> (list/c (box/c integer?)) any) (λ (x) (unbox (car x))) 'pos 'neg) (list (box "not an integer"))) you get an error message that has this text in the middle: in: the content of the 1st element of

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

2015-01-19 Thread Alexis King
I already used blame-add-context, but the message I used wasn’t very good, so I’ve improved it. If everything else looks good, feel free to merge this whenever you get the chance! > On Jan 19, 2015, at 15:52, Robby Findler wrote: > > Ah: one other note. When you do something like this: > > ((

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

2015-01-19 Thread Robby Findler
Oh, sorry I missed that. Robby On Mon, Jan 19, 2015 at 6:40 PM, Alexis King wrote: > I already used blame-add-context, but the message I used wasn’t very good, so > I’ve improved it. If everything else looks good, feel free to merge this > whenever you get the chance! > >> On Jan 19, 2015, at