This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-09-20
Channels
- # announcements (5)
- # beginners (37)
- # calva (3)
- # cider (23)
- # clojure (98)
- # clojure-dev (16)
- # clojure-europe (5)
- # clojure-italy (4)
- # clojure-nl (5)
- # clojure-spec (7)
- # clojure-uk (52)
- # clojurescript (14)
- # cursive (15)
- # data-science (1)
- # datomic (20)
- # emacs (7)
- # flambo (2)
- # fulcro (10)
- # jackdaw (1)
- # jobs (3)
- # joker (2)
- # juxt (3)
- # keechma (3)
- # leiningen (8)
- # luminus (3)
- # music (1)
- # off-topic (83)
- # pathom (19)
- # re-frame (19)
- # reitit (4)
- # shadow-cljs (76)
- # spacemacs (95)
- # tools-deps (16)
Well, the full generality of spec allows arbitrary code in predicates, so it is in general computationally undecidable to statically check that a program meets such a general spec.
spec has been designed with run-time checking (and generation, etc.) in mind, not trying to limit itself to what can be statically checked, although subsets of it can be: https://github.com/arohner/spectrum
Because folks keep asking about our "coercing specs" at work, we just open-sourced them https://github.com/worldsingles/web-specs worldsingles/web-specs {:mvn/version "0.1.0"}
Nope, none at all. I originally submitted a talk to Conj about it (and it was accepted) but I pulled it because Alex was so "anti" the whole conformer thing. That was years ago. But I still think we made the right decision and I'd stand by it every day.