This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-01-07
Channels
- # announcements (3)
- # beginners (124)
- # calva (60)
- # cider (81)
- # cljs-dev (65)
- # cljsrn (1)
- # clojure (268)
- # clojure-dusseldorf (2)
- # clojure-europe (3)
- # clojure-italy (9)
- # clojure-losangeles (1)
- # clojure-nl (22)
- # clojure-russia (3)
- # clojure-spec (24)
- # clojure-uk (34)
- # clojurescript (72)
- # code-reviews (8)
- # cursive (20)
- # datomic (32)
- # fulcro (49)
- # jobs (1)
- # jobs-discuss (15)
- # juxt (10)
- # lein-figwheel (10)
- # nrepl (4)
- # off-topic (37)
- # overtone (1)
- # portkey (2)
- # protorepl (8)
- # random (1)
- # re-frame (1)
- # reagent (43)
- # reitit (8)
- # ring (16)
- # ring-swagger (2)
- # rum (6)
- # shadow-cljs (63)
- # specter (2)
- # testing (32)
- # tools-deps (32)
- # unrepl (1)
- # vim (3)
@mathpunk a minor thing, the require block makes this line redundant
using alias for keyword namespaces that don't exist as code namespaces is a nice trick though - it would likely make other namespaces clearer (I assume they were written before you discovered this trick)
I think so. What I was going for is, there were certain ideas that seemed distinct sub-ideas --- like the idea of counting failures --- but that were just data and didn't need functions
here if you used io/resource you could reliably point to something inside the repo (but perhaps it's intentional also that the sample data is not in the repo) https://github.com/mathpunk/cyclotron/blob/master/src/cyclotron/utils.clj#L11
but I also see io/as-file io/resource "reports" elsewhere which doesn't reflect anything visible in the repo