This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-01-10
Channels
- # announcements (15)
- # bangalore-clj (1)
- # beginners (207)
- # calva (22)
- # cider (4)
- # clara (73)
- # cljs-dev (7)
- # cljsrn (4)
- # clojure (125)
- # clojure-dev (38)
- # clojure-europe (2)
- # clojure-india (11)
- # clojure-italy (11)
- # clojure-nl (14)
- # clojure-russia (22)
- # clojure-uk (32)
- # clojurescript (30)
- # cursive (11)
- # datavis (2)
- # datomic (14)
- # editors (3)
- # emacs (3)
- # hyperfiddle (4)
- # juxt (13)
- # klipse (1)
- # luminus (5)
- # nrepl (7)
- # off-topic (9)
- # overtone (13)
- # portkey (1)
- # re-frame (15)
- # reagent (13)
- # ring (30)
- # schema (4)
- # shadow-cljs (108)
- # spacemacs (8)
- # specter (3)
- # sql (2)
- # testing (11)
- # tools-deps (21)
- # unrepl (4)
Has anyone built something that hashes the raw forms of code and re-runs quickcheck (or generative tests) only when the hashes change? It sounded to me like Rich was hinting at something like this in Spec-ulation.
hashing the raw forms is not enough, in theory you'd want to track changes in all potential dependencies
with something like https://github.com/Bronsa/tools.analyzer.jvm.deps probably
^ What's codeq2. (My meager google foo didn't yield anything 🙂)
Thank you guys for introducing me to this awesome thing.
This is the podcast link if anyone's interested:
Now I remember what Rich was talking about here: