This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-02-16
Channels
- # aleph (2)
- # beginners (68)
- # boot (25)
- # bristol-clojurians (5)
- # cider (10)
- # cljs-dev (60)
- # cljsrn (1)
- # clojure (138)
- # clojure-austin (1)
- # clojure-france (2)
- # clojure-greece (11)
- # clojure-italy (4)
- # clojure-russia (16)
- # clojure-spec (4)
- # clojure-uk (75)
- # clojurescript (26)
- # core-async (28)
- # cursive (25)
- # data-science (4)
- # datomic (16)
- # defnpodcast (2)
- # devops (2)
- # docs (10)
- # duct (11)
- # emacs (1)
- # events (1)
- # figwheel (8)
- # fulcro (61)
- # garden (2)
- # hoplon (6)
- # java (6)
- # jobs-discuss (1)
- # lein-figwheel (14)
- # leiningen (86)
- # luminus (11)
- # off-topic (8)
- # parinfer (9)
- # pedestal (2)
- # re-frame (19)
- # reagent (1)
- # ring (3)
- # ring-swagger (8)
- # shadow-cljs (278)
- # spacemacs (13)
- # sql (5)
- # testing (7)
- # unrepl (8)
- # yada (25)
Thanks for your comment. I've seen your code with categorization before. That's the same concept. The other one is used by quil
author, but he uses two tags: category and subcategory and you can put your var into one category.
For examples, I understand that more sophisticated examples should be separated and embedded in separated documents, tutorials etc.
My goal was to enable something which can be called "unit examples". I need something which can illustrate one function at once to build reference like documentation.
like this page for example: https://processing.org/reference/quad_.html
interesting... it should be possible to use the machinery I built up in https://github.com/arrdem/stacks to execute an example again as a test. that's basically how the doctests system I prototyped out works, it just added some syntax sugar for writing assertions tersely.