On Tue, Mar 29, 2011 at 1:01 AM, Kevin Tew <t...@cs.utah.edu> wrote: > Being able to sync on when they terminate? > Thats pretty easy to add, I should do it. > > Place currently is an event you can sync on, but it becomes ready when a > message arrives. Not when it terminates.
Oh, in that case I don't see a problem with the current API. I guess it's a little weird that a `place?' is both an appropriate argument to `place-wait' and to `place-recv', but I don't know if it's a good idea to make both of those actions events. In any case, you might want to add places to the big list of primitive things that are events in the event documentation. > On 03/28/2011 05:34 PM, Sam Tobin-Hochstadt wrote: >> >> Not a bug or crash, but it would be nice if a `place' was an event, in >> the sense of `evt?'. Come to think of it, this would be good for >> `future' as well. >> >> On Mon, Mar 28, 2011 at 1:08 PM, Kevin Tew<t...@cs.utah.edu> wrote: >>> >>> I would like to make --enable-places the default in the near future. >>> >>> I would appreciate it, if racket developers could configure and build >>> with >>> --enable-places >>> and report any bugs or crashes. >>> >>> Thanks, >>> Kevin >>> >>> _________________________________________________ >>> For list-related administrative tasks: >>> http://lists.racket-lang.org/listinfo/dev >>> >> >> > > -- sam th sa...@ccs.neu.edu _________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
