Hmm, wonder why into has a single argument version: ([to] to)

Probably because then (into something) is the same as (into something []) ?

reduce into

@schmee I saw your announcement of daguerreo. Since tasks typically take a little while, and have side effects, it would be nice to have a mechanism to check that I have specified the correct dependencies. Now, if I need :diced-mango (in the README example) I need to specify :dice-mango as a dependency. And I need to know that :blend is the task that provides me with :smoothie, etc. Have you any thought on how to accomplish any "integrity" check of the job?

what's the 'idiomatic' way of removing a tap which I've lost a reference to?

eg. I define a tap function

(defn my-tap [x]
  (print (keys x)))
(add-tap my-tap)

then realise I made a mistake and go back to re-eval my-tap

(defn my-tap [x]
  (println (keys x)))

now I can't use remove-tap to get rid of the initial tap fn, because #'my-tap points to the new fn

under the hood there's a clojure.core/tapset atom which holds all the taps, but even that's private so I can't reset it without resorting to some namespace hack

iiuc, there isn't an idiomatic way -- what you mentioned at the end about the namespace hack is the only way i know of -- happy to hear otherwise 🙂

Would there be a reasonable way of writing something like python's functools.wraps in clojure?

im occasionally frustrated that the naming of wrapped functions goes to annonymous gibberish

case in point this function

@emccue Where is the gibberish?

@emccue you could pass the :doc and :arglists keys of the original function metadata to the new function

@emccue You want a macro for that. You can resolve the symbol to its var and get the metadata.

you can name functions

(fn cached-function [& args]

@vale I think he wants the name of the passed in function.

oh. if the function is passed in then you don't even need macros, you already have the function "object" in your hands

But not the name and doc string.

i could do a regex on the tostring

it would be evil but i can do it

Funny encapsulation experiment:

(ns encapsulate)

(defn encapsulate [x]
  (if (instance? clojure.lang.IObj x)
    (let [ns *ns*]
      (vary-meta x assoc :type ::encapsulated ::ns ns))
    x))

(defmethod print-method ::encapsulated [x writer]
  (if (= *ns* (::ns (meta x)))
    (print-method (vary-meta x dissoc :type ::ns) writer)
    (print-method "***" writer)))

(ns boop)
(def x (encapsulate/encapsulate {:a 1}))
(prn x) ;; => {:a 1} 

(ns woop)
(prn boop/x) ;; => "***"

I know there is a popular idea that there is no much value in encapsulation when all you have is immutable values, but I still sometimes find it useful to use "soft" encapsulation as a way to say "treat this value as a black box, it's shape is implementation detail that belongs to that namespace only"

@vlaaad I use namespaced keys for that.

it's a PoC 🙂

is there anyone using Open JDK in production with Clojure? what are the odds of oracle changing its license and end up killing it? I ran into this discussion today with one of my friend who is moving from JVM to Elixir/beam. because he does not trust oracle anymore.

I don't have much experience with JVM and its ecosystems. I am looking for your thoughts and point of view. Thanks

no problem with the license

it's GPL... forever, many different companies behind it

RedHat, Amazon (corretto), Azul, IBM

moving from JVM to Beam is a far bigger risk IMHO

Used OpenJDK, using amazon corretto for some stuff now

@ghadi Oh thanks that clears it up

ever since I upgraded java from 8 to 12 I've been getting a lot of errors in lein plugins:

Caused by: Syntax error compiling deftype* at (clojure/core/rrb_vector/rrbt.clj:282:1).
	at clojure.lang.Compiler.analyzeSeq(Compiler.java:7115)
	at clojure.lang.Compiler.analyze(Compiler.java:6789)
Caused by: java.lang.IllegalArgumentException: Must hint overloaded method: toArray
	at clojure.lang.Compiler$NewInstanceMethod.parse(Compiler.java:8497)

yeah, they added a new Collection toArray arity that made certain calls ambiguous re reflection that were not previously ambiguous

that particular error above was fixed in latest rrb-vector iirc

so I have added dependency to rrb-vector 0.0.14, now it works

Is there a function somewhere to test whether one nested data structure is a subset of another? e.g. if the left has a key, the right must, recursively?

leaves are =.

I do not know of anything exactly like that included with Clojure. clojure.data/diff has some similarities to what you are asking, but looks for differences recursively between two values.

oh, I think that's exactly what I need.

If not, you can copy its code and tweak it to your heart's desire.

I have a function kind of like that here: https://github.com/clojure/spec.alpha/blob/master/src/test/clojure/clojure/test_clojure/spec.clj#L17

specifically for nested maps really. this is testing code so it's kind of tailored to the job of "is the stuff I'm looking for a subset of the nested maps that I got"

well, same situation here: characterization tests that ensure that I don't break existing bus messages, where I can add fields but not remove them or change them.

diff ends up being nice, because I can say (is (empty? (unmet-requirements msg requirements))), where unmet-requirements returns just the things only in requirements.

Then, test errors are nice to parse.

also perhaps nice to print/save the differences if a problem arises, for debugging

there are interesting choices for stuff like this in collection values. Rich and I have talked about adding something like this to clojure itself (flip the args and maybe call it subsumes? or something)

Seems related to the data shape problem from Rich's last conj talk.

yep