This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-02-28
Channels
- # aleph (50)
- # announcements (3)
- # aws (35)
- # beginners (74)
- # boot (25)
- # calva (39)
- # cider (18)
- # clara (2)
- # cljdoc (18)
- # cljs-dev (24)
- # cljsrn (11)
- # clojure (166)
- # clojure-europe (13)
- # clojure-italy (5)
- # clojure-nl (6)
- # clojure-spec (35)
- # clojure-uk (263)
- # clojurescript (22)
- # clojutre (1)
- # code-reviews (34)
- # cursive (58)
- # data-science (2)
- # datascript (4)
- # datomic (4)
- # duct (6)
- # emacs (7)
- # figwheel-main (9)
- # fulcro (2)
- # graphql (3)
- # hoplon (22)
- # hyperfiddle (2)
- # juxt (5)
- # kaocha (6)
- # leiningen (33)
- # luminus (15)
- # off-topic (1)
- # pedestal (5)
- # reagent (18)
- # reitit (12)
- # shadow-cljs (171)
- # vim (5)
I don’t have much to add to the above - as the examples shows, Clara doesn’t try to query further into facts, it just treats them as top level entities to be joined, inserted, etc.
Right now my understanding of it makes me basically think it's like calling `iterate` on a set of data until it doesn't change anymore (applying rules) and then filtering it (the queries).
That sounds on target. One thing a rules engine such as Clara is good at is efficiently applying small changes onto a complex ruleset - the intermediate states of the rule engine internals are kept to facilitate this. The “truth maintenance” page on the webpage is a good one to read if you haven’t yet. @bmaddy