dsimcha Wrote:
> == Quote from Sean Kelly (s...@invisibleduck.org)'s article
> > Álvaro Castro-Castilla Wrote:
> > >
> > > Language extensions for message passing, such as Kilim for Java send
> > > messages
> giving away the ownership of data, not copying it. That's a reason for the
> need of
>
dsimcha:
> The exception, though, is when someone is using a construct that would only be
> used by people who really need efficiency, and thus has already explicitly
> asked
> for efficiency. This includes parallel foreach. In these cases, I think that
> "efficiency first, safety second" has to
== Quote from Sean Kelly (s...@invisibleduck.org)'s article
> �lvaro Castro-Castilla Wrote:
> >
> > Language extensions for message passing, such as Kilim for Java send
> > messages
giving away the ownership of data, not copying it. That's a reason for the need
of
compiler/runtime support.
> Know
Álvaro Castro-Castilla Wrote:
>
> Language extensions for message passing, such as Kilim for Java send messages
> giving away the ownership of data, not copying it. That's a reason for the
> need of compiler/runtime support.
Knowledge of unique ownership can obviate the need for copying, but co
Sean Kelly Wrote:
> dsimcha Wrote:
>
> > == Quote from Sean Kelly (s...@invisibleduck.org)'s article
> > > dsimcha Wrote:
> > > >
> > > > This is great for super-scalable concurrency, the kind you need for
> > > > things like
> > > > servers, but what about the case where you need concurrency mo
dsimcha Wrote:
> == Quote from Sean Kelly (s...@invisibleduck.org)'s article
> > dsimcha Wrote:
> > >
> > > This is great for super-scalable concurrency, the kind you need for
> > > things like
> > > servers, but what about the case where you need concurrency mostly to
> > > exploit data
> > > p
== Quote from Sean Kelly (s...@invisibleduck.org)'s article
> dsimcha Wrote:
> >
> > This is great for super-scalable concurrency, the kind you need for things
> > like
> > servers, but what about the case where you need concurrency mostly to
> > exploit data
> > parallelism in a multicore enviro
dsimcha Wrote:
>
> This is great for super-scalable concurrency, the kind you need for things
> like
> servers, but what about the case where you need concurrency mostly to exploit
> data
> parallelism in a multicore environment? Are we considering things like
> parallel
> foreach, map, reduce
== Quote from Sean Kelly (s...@invisibleduck.org)'s article
> �lvaro Castro-Castilla Wrote:
> > Andrei Alexandrescu Wrote:
> >
> > > http://my.safaribooksonline.com/roughcuts
> > >
> > > The current version includes virtually the entire book except (a)
> > > overloaded operators, (b) qualifiers, (c
Álvaro Castro-Castilla Wrote:
> Andrei Alexandrescu Wrote:
>
> > http://my.safaribooksonline.com/roughcuts
> >
> > The current version includes virtually the entire book except (a)
> > overloaded operators, (b) qualifiers, (c) threads. In the meantime I
> > have finished the new design and wro
Andrei Alexandrescu Wrote:
> http://my.safaribooksonline.com/roughcuts
>
> The current version includes virtually the entire book except (a)
> overloaded operators, (b) qualifiers, (c) threads. In the meantime I
> have finished the new design and wrote the chapter on overloaded
> operators. Th
Andrei Alexandrescu:
> The initial framework will emphasize de facto
> isolation between threads and message passing. It will build on an
> Erlang-inspired message passing design defined and implemented by Sean.
Sounds good. When you have 30+ CPU cores you don't want shared memory, in those
si
http://my.safaribooksonline.com/roughcuts
The current version includes virtually the entire book except (a)
overloaded operators, (b) qualifiers, (c) threads. In the meantime I
have finished the new design and wrote the chapter on overloaded
operators. The design got Walter's seal of approval
13 matches
Mail list logo
