This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-05-30
Channels
- # admin-announcements (4)
- # alda (49)
- # beginners (42)
- # boot (55)
- # cider (33)
- # cljs-dev (4)
- # cljsjs (3)
- # cljsrn (152)
- # clojure (92)
- # clojure-belgium (3)
- # clojure-brasil (18)
- # clojure-dusseldorf (32)
- # clojure-france (2)
- # clojure-greece (10)
- # clojure-japan (1)
- # clojure-mexico (1)
- # clojure-russia (50)
- # clojure-sg (1)
- # clojure-spain (1)
- # clojure-spec (12)
- # clojurescript (262)
- # core-async (2)
- # cursive (7)
- # datomic (79)
- # emacs (16)
- # euroclojure (2)
- # events (1)
- # hoplon (260)
- # jobs (2)
- # jobs-discuss (1)
- # keechma (7)
- # luminus (8)
- # mount (7)
- # off-topic (3)
- # om (101)
- # onyx (33)
- # re-frame (34)
- # reagent (10)
- # slack-help (4)
Makes me wonder what would happen if we applied specs to the ClojureScript compiler’s analysis metadata map (like Sebastian’s defrecord
work but re-cast and enriched as specs). The compiler would be dog-slow checking for conformance of that gigantic map, but it would be interesting to run the unit test suite with instrumentation enabled.
spec
works perfectly in self-host (KLIPSE). A lot of live coding examples using cljs version 1.8.51 and loading cljs spec
code from github: http://blog.klipse.tech/clojure/2016/05/30/spec.html
Thx @dnolen Actually you did the amazing self host 👏