This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-12-10
Channels
- # 100-days-of-code (2)
- # adventofcode (188)
- # aleph (3)
- # announcements (2)
- # beginners (76)
- # boot (3)
- # braveandtrue (49)
- # cider (82)
- # clara (15)
- # clojure (101)
- # clojure-europe (4)
- # clojure-india (3)
- # clojure-italy (26)
- # clojure-kc (1)
- # clojure-nl (4)
- # clojure-norway (1)
- # clojure-russia (5)
- # clojure-uk (33)
- # clojurescript (32)
- # crypto (20)
- # cursive (34)
- # datomic (45)
- # emacs (3)
- # events (1)
- # figwheel (1)
- # figwheel-main (10)
- # fulcro (30)
- # graphql (14)
- # hoplon (12)
- # hyperfiddle (21)
- # jobs (11)
- # kaocha (7)
- # klipse (8)
- # leiningen (10)
- # luminus (3)
- # nrepl (18)
- # off-topic (232)
- # onyx (8)
- # pathom (6)
- # re-frame (30)
- # reagent (3)
- # reitit (6)
- # remote-jobs (3)
- # ring-swagger (4)
- # shadow-cljs (21)
- # spacemacs (5)
- # sql (18)
- # tools-deps (23)
- # yada (2)
AFAICT, I have a situation where a [:not [:or A B]] is being ignored on a rule. Any thoughts about how to troubleshoot this?
@eraserhd there are certainly some issues that can happen with negated complex conditions.
I'm definitely simplifying. We're working on making a small reproduction. Maybe it'll go away, or we'll figure out we're doing something boneheaded. :D
But in general Clara compiler will try to convert things into disjunctive normal form.
Sometimes there may be issues with doing this when variable bindings are used across clauses that are moving around.
It may or may not relate to your issue. I just think there were perhaps still a few edge cases pointed out in some gh issues outstanding
I often will just advocate for breaking more complex expressions into separate rules that have intermediate facts between them to recreate the logic you are looking for