have two async functions use the same global var and you will completely reproduce the problem described here
-
-
Replying to @mountain_ghosts
these solutions all address shared state. "shared state" is two concepts: message passing removes "shared", FP removes "state"
1 reply 0 retweets 2 likes -
-
Replying to @mountain_ghosts
all the canonical classes of consistency/concurrency issues can happen in JS programs quite easily
1 reply 0 retweets 1 like -
Replying to @mountain_ghosts
it's possible I'm misunderstanding "data races" since the author distinguishes them from "race conditions"
4 replies 0 retweets 0 likes -
Replying to @mountain_ghosts
@mountain_ghosts http://blog.regehr.org/archives/490 does a good job of explaining the distinction1 reply 0 retweets 3 likes -
Replying to @steveklabnik
.
@steveklabnik so a data race is a very specific type of race condition?3 replies 0 retweets 1 like -
Replying to @mountain_ghosts
@mountain_ghosts correct. data races can be prevented by compilers, race conditions can't1 reply 1 retweet 1 like -
-
Replying to @mountain_ghosts
@mountain_ghosts np. this is my life now, because rust prevents data races but not race conditions, heh. still trying to explain it better1 reply 0 retweets 3 likes
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
