Tony Morris

@runarorama thought about your dream: concurrency needs side effects, parallelism does not. Actors=concurrency dataflow=parallelism

@rolandkuhn @runarorama not true at all! Haskell does concurrency, no side-effects. Should take a look.

@puffnfresh where precisely shall I look?

@rolandkuhn and Haskell has recently got a library for primitives for Erlang style concurrency: http://haskell-distributed.github.io/ 

@puffnfresh "put" captures local effect but not the effect on the other thread, hence hidden side-effect which makes reasoning so hard

@rolandkuhn putMVar has the effect in IO so equational reasoning is absolutely not broken. No side-effects.

@puffnfresh @rolandkuhn fwiw, non-determinism does not necessitate a lack of referential transparency.

@runT1ME @puffnfresh but then your function does not sufficiently express your intent any more, concurrent comp. is not referentially transp