This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-08-31
Channels
- # aleph (38)
- # beginners (91)
- # boot (4)
- # cider (20)
- # clara (11)
- # cljs-dev (4)
- # clojure (179)
- # clojure-greece (1)
- # clojure-italy (16)
- # clojure-portugal (1)
- # clojure-russia (1)
- # clojure-sanfrancisco (1)
- # clojure-spec (183)
- # clojure-uk (50)
- # clojurescript (111)
- # core-async (24)
- # cursive (4)
- # datascript (11)
- # datomic (29)
- # fulcro (120)
- # gorilla (2)
- # jobs (1)
- # keechma (2)
- # keyboards (26)
- # leiningen (4)
- # luminus (7)
- # lumo (15)
- # off-topic (2)
- # onyx (31)
- # parinfer (12)
- # portkey (1)
- # protorepl (1)
- # re-frame (50)
- # reagent (106)
- # remote-jobs (1)
- # ring-swagger (2)
- # rum (10)
- # spacemacs (17)
- # sql (16)
- # test-check (1)
- # yada (2)
is it safe to call insert!
from different threads? e.g., within a future
? I have a way to not need this (e.g., gather data with the future and then insert! from the main thread), I'm more just curious.
I do think that implementation-wise, as long as every thread has fully completed their r/insert!
prior to r/fire-rules
it may work
So in general, during the “fire rules loop” cycle of the rules engine, the memory is in a mutable state
This is done primarily for performance. The caller perceives the working memory to be a persistent, immutable data structure that is returned after each call to r/fire-rules
on a given sesion