[racket-dev] chaperone-evt restrictions?

From: Asumu Takikawa (asumu at ccs.neu.edu)
Date: Fri Aug 2 18:40:18 EDT 2013

On 2013-08-02 18:32:38 -0400, Asumu Takikawa wrote:
> I'm currently trying to implement contracts for synchronizable events.
> During that, I've discovered that there seems to be an undocumented
> restriction that `chaperone-evt` can only chaperone an event that is not
> a handle event. Here's an example:

I just realized this was supposed to be worded as a question, but I
forgot to include the question: is this a fundamental limitation that I
should work around in the type/contract system or can it be changed?


Posted on the dev mailing list.