Generally, the first suggestion for questions like this tends to be: try to write it as a function first, rather than a macro. You might want a macro to provide a little "syntactic sugar" over the function later, but try to write a plain function first.

@U03TDQ043GA Cambium has a macro with-logging-context to do something similar. Maybe that would be useful? Also, there's #cambium channel for Cambium discussion.

@U066J7E2U Hey Shantanu, we are actually using Cambium core for this purpose but with each time I use with-logging-context macro I have to rearrange the attributes as per the schema, I was told by my lead that it's repetitive and you should write a macro to handle this restructuring. Also, I really appreciate the work you are doing in Clojure, I have been through couple of your articles when I started with Clojure and they are great.

Do you mean like https://clojuredocs.org/clojure.core/when?

Oh Yah! I forgot it :hugging_face: thanks.

There is also (if condition something), although there is some difference of opinion among Clojurians whether if or when is preferable in that situation, perhaps depending upon whether the something has side effects or not. As far as the language itself is concerned, (if condition something) and (when condition something) are identical, but some people want there to be additional information conveyed by the choice of if or when.

Which of the two is meant to indicate side effects?

The language itself does not distinguish this at all, but if I recall correctly, some people argue that it is preferable to use when when the body performs side effects

Here is probably more discussion and reading material on the subject than most people are likely to want to read: https://stackoverflow.com/questions/25948511/when-to-use-if-and-when-in-clojure

persistentlist.primordial is list i think. You're probably doing something like (conj list 1) instead of (conj (list) 1)

i remember seeing a doc on common clojure errors but i can't find it anymore. For those "X cannot be cast to class Y" it's quite useful to know the common clojure interfaces to decrypt those quickly (clojure.lang.IFn, clojure.lang.IPersistentVector, etc)

Yes thanks list seems to be root. I was trying rich4clojure problem-153 which has some very awkward tests where you have to compare sets of sets. I am making some checks to see if more than one of the included sets include false as an element

you don't really ever need to convert sets to lists, most clojure functions will work on collections by calling seq As a note: technically not exactly the same but you could simply do (map seq #{#{(= "true") false} ...})

So far (def lst-sets (map seq #{#{(= "true") false} #{:yes :no} #{(class 1) 0} #{(symbol "true") 'false} #{(keyword "yes") ::no} #{(class '1) (int \0)}})) (defn two+false "Given a sequence of booleans test for two or more false" [bol-seq] (< 1 (reduce (fn [acc bol-seq] (if (= false bol-seq) (inc acc) acc)) 0 (next bol-seq)))) (two+false (map (partial not-any? ; check if each set has any false elements #(= false %)) lst-sets))

lein run is trying to read the clojure code and it found something it didn't understand, which is what it says here

so we would have to look at that introduction_to_clojure/core.clj line 32 to learn more. Or the rest of the stacktrace might give us a hint.

Hey Drew! Eric got back to me and clarified that this is a bug that he has yet to check out. Unfortunately, I have no idea why it’s behaving like this. Fortunately, I was able to go thru the exercises with the repl via terminal, and just added functions that were missing to get to the next step

Glad to hear you got the help you needed.