This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-07-12
Channels
- # babashka (6)
- # beginners (23)
- # calva (27)
- # cider (1)
- # clj-kondo (23)
- # cljsrn (2)
- # clojars (4)
- # clojure (90)
- # clojure-dev (8)
- # clojure-europe (1)
- # clojure-serbia (1)
- # clojure-spec (2)
- # clojurescript (9)
- # code-reviews (7)
- # core-async (1)
- # cursive (4)
- # datomic (13)
- # emacs (2)
- # hoplon (28)
- # juxt (12)
- # leiningen (1)
- # malli (22)
- # nrepl (3)
- # off-topic (51)
- # reitit (8)
- # shadow-cljs (16)
- # spacemacs (25)
- # sql (4)
- # test-check (5)
- # tools-deps (5)
I think that the source code would have been easier to read if the rose tree was named after its purpose, for example shrink-tree
fwiw, quickcheck in haskell seems to use the term "rose" as well: https://hackage.haskell.org/package/QuickCheck-2.9/docs/Test-QuickCheck-Property.html#g:4 - i was initially puzzled but found a wikipedia page: https://en.m.wikipedia.org/wiki/Rose_tree
also the docs of the corr ns say: https://github.com/clojure/test.check/blob/master/src/main/clojure/clojure/test/check/rose_tree.cljc#L11
in this case i was initially lost but the name actually helped me to find relevant related info
yeah the initial draft of test.check was heavily based on quickcheck