On Tue, Mar 29, 2011 at 7:46 AM, Sam Tobin-Hochstadt <sa...@ccs.neu.edu> wrote: > On Tue, Mar 29, 2011 at 8:42 AM, Robby Findler > <ro...@eecs.northwestern.edu> wrote: >> On Mon, Mar 28, 2011 at 6:34 PM, Sam Tobin-Hochstadt <sa...@ccs.neu.edu> >> 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. >> >> FWIW, this will probably never happen for futures, due to future-safe >> issues. Using events in a future is currently far far far from being >> future safe. > > I wasn't thinking of using events in futures -- that does sound like a > ton of work. I just meant that > > (sync (future (lambda () ...))) > > should be the same as > > (touch (future (lambda () ...))) > > or is that hard for future-safety reasons as well?
I think that wouldn't be hard if you know you're on the main, runtime thread. But if you aren't or if you've put that event into some larger choice or something, then I'm not sure. Robby _________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
