Whoops. - PLT now supports multi-core parallelism via futures. Futures create tasks that run in parallel, as long as the tasks stay in the "fast path" of the runtime system. For more information, see:
http://docs.plt-scheme.org/guide/performance.html?q=future#(part._effective-futures) Robby On Thu, Apr 1, 2010 at 9:30 AM, Matthias Felleisen <[email protected]> wrote: > > Can we please eliminate the word 'true' from this first line? > > > On Apr 1, 2010, at 11:17 AM, Robby Findler wrote: > >> Uhh... okay: >> >> - PLT Scheme now supports true multi-core parallelism via futures. >> Futures create tasks that run in parallel, as long as the tasks stay >> in the "fast path" of the runtime system. For more information, see: >> >> >> http://docs.plt-scheme.org/guide/performance.html?q=future#(part._effective-futures) >> >> Robby >> >> On Thu, Apr 1, 2010 at 9:05 AM, Matthew Flatt <[email protected]> wrote: >>> >>> At Thu, 01 Apr 2010 04:56:35 -0400, Eli Barzilay wrote: >>>> >>>> Matthew: >>>> - Futures are on by default >>>> - wrap each top-level form in a module with a prompt (if visible >>>> enough) >>>> - basic set library >>>> - things from r18375, if visible enough >>>> - scribble/jfp >>> >>> Only futures deserve a bullet I think. Maybe Robby wants to write it? >>> >>> _________________________________________________ >>> For list-related administrative tasks: >>> http://list.cs.brown.edu/mailman/listinfo/plt-dev >>> >> _________________________________________________ >> For list-related administrative tasks: >> http://list.cs.brown.edu/mailman/listinfo/plt-dev > > _________________________________________________ For list-related administrative tasks: http://list.cs.brown.edu/mailman/listinfo/plt-dev
