At that point, might as well give the parameter a name...

Even if it is something as simple as x

The (number? %) (zero? %) clause is functionally equivalent to testing (and (number? %) (zero? %)) outside the cond

Same with the following clause

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!)

Not quite sure what you'd call the 'sequential-or-string' version

Then your empty check becomes (or (empty-number? %) (empty-sequential? %) (nil? %))

Or if you really wanna have fun

#(apply or ((juxt empty-number? empty-sequential? nil?) %))

Forgot about or being a macro. You get the idea, though. 😛

#((apply some-fn ((juxt empty-number? empty-sequential? nil?) %)))

we are going for maximum “fun” right?

Of course, this won’t fit the intended purpose because juxt is non-lazy, but I like the spirit 🙂

Make it stranger! ™️

How does one call [org.clojure/clojure “…”], a coordinate? Maven coordinate?

@borkdude it's from Maven: https://maven.apache.org/pom.html#Maven_Coordinates

GAV is a coordinate tuple (group, artifact, version)

What is the common term for this in clojure tooling? I’m writing a README

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.

I’m not remembering the name of a lein plugin

it automatically re-runs your tests, especially the failing ones, quickly, by reloading only the changed ones

it’s not lein auto, because that just does lein test again

it’s not lein retest, because that doesn’t do the fast reloading IIRC

(also hasn’t been touched since 2011 and apparently has outstanding bugs on current clojure setups)

[com.jakemccrary/lein-test-refresh "0.17.0”] !