News for hackers. Stuff that matters.
Re:Fix your damned data races by zaphar on Tuesday February 24, 2015 @10:38AM (#9101142)
No, Functional languages reduce the problems surface area but they don't eliminate it. You can still get data races and deadlocks in Haskell. They aren't the same as a memory race in say C where the contents of a variable might change out from under you in truly bizarre ways but you still get algorithmic races where the wrong answer comes our the other end because two parallel operations happened in the wrong order.
Re:Fix your damned data races by marcosdumay on Tuesday February 24, 2015 @11:36AM (#9101673)
You can't get deadlocks and data races on pure code.

Once your code is in a monad, every one of those problems may be back (including memory race).

Re:Fix your damned data races by elihu on Tuesday February 24, 2015 @01:50PM (#9102667)
The IO monad in particular. Monads by themselves don't introduce races/deadlocks.
Re:Fix your damned data races by rthomas6 on Tuesday February 24, 2015 @10:55AM (#9101314)
>two parallel operations happened in the wrong order.

I thought separate functions weren't allowed to have dependencies like this?

Re:Fix your damned data races by taeric on Tuesday February 24, 2015 @11:23AM (#9101567)
Simply put, not everything is commutative.