Re: What To Do About Shared?

2011-03-23 Thread Don
dsimcha wrote: == Quote from Don (nos...@nospam.com)'s article Seems to me, that you're making use of some primitive that I'll call a 'DivisableArray' -- an array that can be sliced up (into other DivisibleArrays), and different DivisableArrays can be sent to different threads. You can extract a

Re: What To Do About Shared?

2011-03-23 Thread Andrei Alexandrescu
On 3/23/11 10:22 AM, Don wrote: dsimcha wrote: == Quote from dsimcha (dsim...@yahoo.com)'s article On 3/23/2011 9:09 AM, Jason House wrote: dsimcha Wrote: Some discussions about std.parallelism have prompted an examination of how far D's guarantees against low level data races should extend

Re: What To Do About Shared?

2011-03-23 Thread dsimcha
== Quote from Don (nos...@nospam.com)'s article > Seems to me, that you're making use of some primitive that I'll call a > 'DivisableArray' -- an array that can be sliced up (into other > DivisibleArrays), and different DivisableArrays can be sent to different > threads. You can extract a normal ar

Re: What To Do About Shared?

2011-03-23 Thread Don
dsimcha wrote: == Quote from dsimcha (dsim...@yahoo.com)'s article On 3/23/2011 9:09 AM, Jason House wrote: dsimcha Wrote: Some discussions about std.parallelism have prompted an examination of how far D's guarantees against low level data races should extend and how safety and practicality s

Re: What To Do About Shared?

2011-03-23 Thread dsimcha
== Quote from dsimcha (dsim...@yahoo.com)'s article > On 3/23/2011 9:09 AM, Jason House wrote: > > dsimcha Wrote: > > > >> Some discussions about std.parallelism have prompted an examination of > >> how far D's guarantees against low level data races should extend and > >> how safety and practicali

Re: What To Do About Shared?

2011-03-23 Thread dsimcha
On 3/23/2011 9:09 AM, Jason House wrote: dsimcha Wrote: Some discussions about std.parallelism have prompted an examination of how far D's guarantees against low level data races should extend and how safety and practicality should be balanced. I didn't follow the review of std.parallelism, c

Re: What To Do About Shared?

2011-03-23 Thread Jason House
dsimcha Wrote: > Some discussions about std.parallelism have prompted an examination of > how far D's guarantees against low level data races should extend and > how safety and practicality should be balanced. I didn't follow the review of std.parallelism, can you give some specific examples?

Re: What To Do About Shared?

2011-03-22 Thread dsimcha
On 3/23/2011 12:36 AM, Graham St Jack wrote: Sounds good in principal. I assume that category a code could be @trusted, and that category b and c must not be @trusted. Right, except for the subset of category C code that does make guarantees. I agree that trying to use the language to discr

Re: What To Do About Shared?

2011-03-22 Thread Graham St Jack
On 23/03/11 11:08, dsimcha wrote: Some discussions about std.parallelism have prompted an examination of how far D's guarantees against low level data races should extend and how safety and practicality should be balanced. On the one hand, coarse-grained multithreading with hard guarantees aga

What To Do About Shared?

2011-03-22 Thread dsimcha
Some discussions about std.parallelism have prompted an examination of how far D's guarantees against low level data races should extend and how safety and practicality should be balanced. On the one hand, coarse-grained multithreading with hard guarantees against low-level races is a great th