This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-04-14
Channels
- # babashka (53)
- # beginners (158)
- # calva (25)
- # cider (21)
- # clara (1)
- # clj-kondo (12)
- # cljsrn (6)
- # clojure (94)
- # clojure-australia (2)
- # clojure-bay-area (6)
- # clojure-europe (40)
- # clojure-nl (10)
- # clojure-spec (16)
- # clojure-uk (18)
- # clojurescript (95)
- # cursive (14)
- # data-science (1)
- # datascript (6)
- # datomic (18)
- # depstar (2)
- # duct (36)
- # emacs (15)
- # events (4)
- # fulcro (16)
- # graalvm (10)
- # helix (25)
- # honeysql (6)
- # jackdaw (4)
- # jobs (2)
- # leiningen (24)
- # lsp (4)
- # malli (10)
- # off-topic (3)
- # pathom (3)
- # polylith (19)
- # practicalli (4)
- # prelude (1)
- # re-frame (6)
- # reagent (13)
- # reitit (3)
- # remote-jobs (10)
- # ring (12)
- # ring-swagger (2)
- # shadow-cljs (54)
- # testing (17)
- # tools-deps (10)
- # xtdb (14)
In terms of Clara having truth maintenance by default, note that whether truth maintenance is used determined by whether insert! or insertion-unconditional! is used, either of which the user opts into. Since we generally feel that using truth maintenance is a better starting point, that is what examples in docs etc. tend to use. In terms of logic on entering a state or leaving it, do you mean within a rules session fire-rules call or between calls? In the case of the former, note that the guarantees from Clara concern the final state after fire-rules complete, not intermediate states. It tries to avoid creating states during fire-rules that will need to be retracted before returning for performance reasons, but this is expected behaviour in some cases. So something like (defrule yourrule …. (state-change-when-activated!)) may not behave as you expect. Otherwise perhaps between fire-rules calls you could run a query and store the result?