This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-02-22
Channels
- # beginners (55)
- # cider (22)
- # cljs-dev (123)
- # cljsrn (75)
- # clojars (1)
- # clojure (92)
- # clojure-europe (2)
- # clojure-italy (16)
- # clojure-nl (6)
- # clojure-spec (17)
- # clojure-uk (77)
- # clojured (2)
- # clojurescript (39)
- # core-async (8)
- # cursive (4)
- # data-science (1)
- # datomic (22)
- # duct (4)
- # editors (21)
- # emacs (10)
- # events (4)
- # fulcro (116)
- # graphql (8)
- # immutant (3)
- # jackdaw (1)
- # juxt (3)
- # kaocha (4)
- # luminus (1)
- # mount (1)
- # nrepl (32)
- # off-topic (34)
- # other-languages (5)
- # pedestal (32)
- # reagent (1)
- # ring (6)
- # ring-swagger (7)
- # shadow-cljs (5)
- # spacemacs (3)
- # specter (1)
- # sql (1)
- # vim (21)
So, what is the status of CLJ-2320? In my case I can limp along with s/merge, but this is (according to the issue itself) a 'major' priority but does not appear to have had any activity since last June. OTOH, it doesn't have any votes either. I don't have an account so can't log in to vote anyway...
Also, why would what is effectively a 'logic system' use short circuiting semantics for an 'and' operator???
@jsa-aerial Anyone can create a JIRA account, I believe...
I think s/and
really has to be short-circuiting since some predicates may blow up if they don't have a guard predicate ahead of them...?
@U04V70XH6 Sounds like a likely explanation, but in this context that 'should not happen'. Put another way, that should be up the user's predicates. If a 'guard' operator is wanted - call it 'guard' or some such.
not in spec1, AFAIK
I should probably let Alex answer that, but I believe it will probably be in spec2
my belief is based on previous discussions of this on slack and mailing lists
https://clojurians.slack.com/archives/C1B1BB2Q3/p1550592458214700 https://clojurians.slack.com/archives/C1B1BB2Q3/p1550601206215400
@christian767 I think @bbrinck has done some trickery in expound wrt docstrings on specs....