Thanks for your answers. Guess, I just got a little bit lost after
digging deeper into the whole thing. Just didn't see anymore that the
core problem is mutability. But it's much clearer again now.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To po
The answer would be a mix of A and B, mostly because there seems to be
an assumption that you have to consider concurrency everywhere in
order to be able to have it at some point later. This is not the case.
You do tend to be very explicit about concurrency and only use the
concurrency primitives
On Mar 9, 9:26 am, Nick Wiedenbrueck
wrote:
> I'm still getting started with Clojure and I'm wondering about how one
> should generally go about concurrency and how transparent concurrency
> is in Clojure. So, to me there would be two approaches:
>
> A) Be aware of the parts of your system that wi
I'm still getting started with Clojure and I'm wondering about how one
should generally go about concurrency and how transparent concurrency
is in Clojure. So, to me there would be two approaches:
A) Be aware of the parts of your system that will be concurrent and
only within these parts write con
