This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-13
Channels
- # bangalore-clj (1)
- # beginners (29)
- # boot (13)
- # braveandtrue (5)
- # clara (5)
- # cljs-dev (42)
- # cljsrn (7)
- # clojure (55)
- # clojure-france (46)
- # clojure-nl (11)
- # clojure-portugal (1)
- # clojure-russia (268)
- # clojure-spec (26)
- # clojure-uk (32)
- # clojurescript (173)
- # clr (2)
- # core-async (46)
- # cursive (22)
- # datomic (33)
- # devcards (1)
- # emacs (5)
- # events (8)
- # figwheel (2)
- # flambo (4)
- # instaparse (8)
- # jobs (11)
- # klipse (46)
- # lein-figwheel (3)
- # london-clojurians (2)
- # nrepl (1)
- # off-topic (29)
- # om (4)
- # om-next (8)
- # pedestal (3)
- # rdf (4)
- # re-frame (51)
- # reagent (104)
- # remote-jobs (1)
- # rum (4)
- # schema (2)
- # specter (19)
- # untangled (16)
- # vim (52)
@mike1452 @apbleonard the 2nd variant could actually cause an infinite loop since Clara’s insert!
will do some automatic truth-maintenance which can hang indefinitely if you have a “logical loop"
However, the 1st variant sounds to be more of what you were asking. You have to deal with duplicated inserts yourself. You could have rules all insert some fact like B there, then have some “final”/”outcome" rule(s) or query(s) that use an accumulator that you can make decide which facts are the most relevant or correct when you get into a situation of “contradictions"
However, I think you were also wanting the engine to tell you about these rules so you could remove them perhaps? That would be something you’d probably have to workout yourself. Sounds domain-specific.