This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-10-08
Channels
- # aleph (4)
- # beginners (34)
- # boot (37)
- # cljs-dev (5)
- # cljsrn (8)
- # clojure (31)
- # clojure-austin (3)
- # clojure-greece (4)
- # clojure-spec (11)
- # clojure-uk (1)
- # clojurebridge (2)
- # clojurescript (13)
- # cloverage (22)
- # cursive (9)
- # datascript (2)
- # defnpodcast (2)
- # devcards (12)
- # emacs (1)
- # hoplon (67)
- # off-topic (5)
- # om (3)
- # onyx (36)
- # planck (3)
- # quil (2)
- # testing (1)
- # untangled (4)
- # yada (168)
The (number? %) (zero? %)
clause is functionally equivalent to testing (and (number? %) (zero? %))
outside the cond
In this case, maybe breaking out each of the sub-clauses into its own (and...
test function could simplify things
So (defn empty-number? [x] (and (number? x) (zero? x))
(could simply turn in to (zero? x)
, the number check becomes redundant!)
Then your empty check becomes (or (empty-number? %) (empty-sequential? %) (nil? %))
Of course, this won’t fit the intended purpose because juxt
is non-lazy, but I like the spirit 🙂
GAV is a coordinate tuple (group, artifact, version)
I call it a 'dependency'
I say something like 'add this to your dependencies'
The term 'coordinate' isn't widely used
(not everyone coming to Clojure is cursed with a background knowledge of Maven)
Thanks @malcolmsparks . I needed it for writing the README here. https://github.com/borkdude/boot-bundle
@mahinshaw Thank you, that is very useful. I wonder if there would be appetite for a grpc client library.
it automatically re-runs your tests, especially the failing ones, quickly, by reloading only the changed ones