3 ms·

OK, so I'm seeing the usual concurrency stuff; what I'm not seeing is conflict detection/prevention for parallel stuff, where you don't let two parallel tasks m

• chaostheory 13y ago
  > what I'm not seeing is conflict detection/prevention for parallel stuff, where you don't let two parallel tasks modify the same array element or some such I could be wrong but based on your own article, that doesn't sound like a parallel task. Aren't parallel tasks already assigned work that don't conflict ala map reduce? > "concurrency is dealing with inevitable timing-related conflicts, parallelism is avoiding unnecessary conflicts" did I miss something?
  • _yosefk 13y ago
    Yeah, the question is what if you have a bug - if you thought you were assigning work so that tasks don't conflict but in fact they do. In Map/Reduce you technically can't have this sort of bug, nor can you have it in pure code; restricting the programmer so that such bugs can not be committed is fair enough. If it is in fact possible to have such bugs, as it is with shared mutable memory, then I expect to see tools for finding such bugs.
    • chaostheory 13y ago
      >If it is in fact possible to have such bugs, as it is with shared mutable memory, then I expect to see tools for finding such bugs. Well with the actor model, it is less likely since you're supposed to be passing immutable messages around and you're not coordinating threads around locked resources.