This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-05-07
Channels
- # beginners (71)
- # boot (25)
- # cider (204)
- # clara (18)
- # cljs-dev (10)
- # cljsrn (64)
- # clojure (50)
- # clojure-dev (2)
- # clojure-dusseldorf (1)
- # clojure-india (5)
- # clojure-italy (1)
- # clojure-nl (21)
- # clojure-poland (65)
- # clojure-spec (41)
- # clojure-uk (10)
- # clojurescript (4)
- # core-async (5)
- # cursive (2)
- # datomic (17)
- # duct (8)
- # emacs (8)
- # fulcro (1)
- # graphql (21)
- # hoplon (2)
- # javascript (3)
- # lumo (25)
- # mount (5)
- # off-topic (5)
- # onyx (3)
- # portkey (6)
- # re-frame (15)
- # reagent (5)
- # rum (1)
- # shadow-cljs (198)
- # spacemacs (19)
- # specter (2)
Has anyone explored the area of exploration for why rules left-hand-side did not meet the rules prerequisites for firing of the RHS?
@ben.borders In a way yes. That is, if I understand your question.
Not directly that though, instead you could consider a pattern to create complementary rules to the primary rules. These complementary rules were meant to catch the opposite case of the assertions.
Interesting.. im assuming then there are multiple complements to each core “rule”. maybe the # of complements = the number of left hand constrints or something similar? unless your compllement rule that is generated has more complex logic
I think the structure of generated rules may depend on which sorts of things you need to capture
You could end up writing rules in an alternative fixed format that can generated several “tiers” of rules from it. so there was the typically rule where you tried to match, but then there were tiers of unsatisfied matches where different parts of the rule were successively removed
ah interesting, so you made the rules very granular so that the complements might be easier to generate?
In that example, you can see it’d get carried away if you tried to capture everything perhaps
but maybe you could split the “constraints” you want to test for into logical “chunks”
but you have to capture the case that facts you are joining to may not be satisfied themselves
So you have to basically just come up with a way to structure these aspects you care about, then probably write something to generate the rules via some extra metadata markup on what is hand-written