Re: Parallel ranges, how?

Philippe Sigaud wrote: I don't know if that'd help you, but did you have a look at David Simcha's parallelFuture module? http://cis.jhu.edu/~dsimcha/parallelFuture.html Looked at it now. It's not exactly what I was thinking. parallelFuture foes the foreach in one thread, and work in others,

Re: Parallel ranges, how?

Philippe Sigaud wrote: I don't know if that'd help you, but did you have a look at David Simcha's parallelFuture module? http://cis.jhu.edu/~dsimcha/parallelFuture.html Gosh, dsimcha just made a post on it in the Phobos mailing list.Th

Re: Parallel ranges, how?

I don't know if that'd help you, but did you have a look at David Simcha's parallelFuture module? > > http://cis.jhu.edu/~dsimcha/parallelFuture.html > > Gosh, dsimcha just made a post on it in the Phobos mailing list.That's what I'd call paralle

Re: Parallel ranges, how?

On Sun, May 30, 2010 at 22:59, Simen kjaeraas wrote: > Simen kjaeraas wrote: > > How does the current range system accommodate parallel iteration? >> >> As far as I can see, a context switch could happen between calls to >> popFront and front, thus popping a value off the range before we're >> a

Re: Parallel ranges, how?

Simen kjaeraas wrote: How does the current range system accommodate parallel iteration? As far as I can see, a context switch could happen between calls to popFront and front, thus popping a value off the range before we're able to get its value. Anyone? It seems to me the system is not thre

Parallel ranges, how?

How does the current range system accommodate parallel iteration? As far as I can see, a context switch could happen between calls to popFront and front, thus popping a value off the range before we're able to get its value. -- Simen