Ah, the atom example is not about race conditions (doesn't happen in either CLJ or CLJS for different reasons, compare-and-set! in former and single threaded environment in latter) but it's about having more than one reference to the same mutable value which could lead to chaos/confusion when debugging as to which part of the program is changing a given value in the atom... Makes sense, or am I conflating things?
On Sat, Jul 4, 2015 at 4:51 AM, Leon Grapenthin <[email protected]> wrote: > It seems like you do understand things clearly already. Your observations > are correct. I don't really understand your atom example, though. > > -- > Note that posts from new members are moderated - please be patient with > your first post. > --- > You received this message because you are subscribed to the Google Groups > "ClojureScript" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/clojurescript. > -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/clojurescript.
