This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-05-13
Channels
- # beginners (202)
- # boot (7)
- # cider (14)
- # clara (2)
- # cljs-dev (7)
- # clojure (56)
- # clojure-italy (9)
- # clojure-spec (6)
- # clojure-uk (12)
- # clojurescript (40)
- # core-async (3)
- # datomic (6)
- # duct (1)
- # editors (10)
- # emacs (5)
- # fulcro (24)
- # off-topic (16)
- # onyx (4)
- # pedestal (1)
- # planck (8)
- # portkey (2)
- # re-frame (31)
- # reagent (23)
- # tools-deps (8)
- # vim (3)
I saw this message by you, Alex, on a Reddit discussion: https://www.reddit.com/r/Clojure/comments/8i3hh0/what_is_the_future_of_clojure_in_the_industry/dysixcn/
Would adding the links you gave for Cognitect blog articles on spec, and the videos, to one or both of the spec rationale and spec guide articles be of interest?
Nah, most of it is also in the guide
I have read about some operation in spec doing 'sampling' in its validation/checking of a value against the spec, for better performance (but also, obviously, less precise checking). Is there something in the spec documentation I can look for to remind me where this occurs?
s/every and s/every-kv
Thanks. I see those in the spec guide, and good to see the doc strings for s/every and s/every-kv mention that partial checking property.