Ooooooh :missing keyword. It doesn’t show up in the docs here: https://clojure.github.io/tools.cli/ However I see it in my repl docs now.

This also tripped me up initially. In addition I didn't understand (from reading code) that specs compose entirely bottom up. In a sense even if you don't specifically ask for them. Say you have an attribute spec of A, and a map spec (s/keys) for B. You don't specify in B that you use A (not even as an optional member), but when you validate B and have A in it with an invalid value, then B will be invalid. It makes sense if you try this in a REPL. And I think spec is well designed that way. But I initially didn't internalize this which tripped me up when reading code.

Thanks @U01EFUL1A8M. Yes and I wondered related to your B spec implies A spec example; I seemed to get spec error reports that only say B is faulty with no trace to the root A invalidity. I tried using libs like expound but not sure I know how to drive this spec 'stack' effect?

(juxt :temp :dtof) gives you a handy function

When you map over a map, you get entry pairs.

Like so: [key value]

oh you just have a single map? ((juxt :temp :dtof) {:temp 42.6 :dtof 217.0} . Or just [(:temp m) (:dtof m)]

or even (map m [:temp :dtof]) (or mapv if you really want a vector)

or just use vals

or (map second {:temp 42.6, :dtof 217.0})

OK, vals is perfect !!!

do you care about the order of the values in your map?

ah yes, we can't rely on key ordering in regular maps

my examples may trip you up further

use one of @U11BV7MTK’s solutions like [(:temp m) (:dtof m)]seems quite declarative

I tried it, but here is what I got:

without the map function

[(:temp raw-set) (:dtof raw-set)]

The row-set is a sequence of these maps.

(map (juxt :temp :dtof) raw-set) is my go-to idiom in this case

Thats awesome, that seems to work.

it's not the only way, e.g.: (map #(vector (:temp %) (:dtof %)) raw-set) is what you're trying to do #([(:temp %) (:dtof %)]) is invalid because the # dispatch macro does not work like that, it's like trying to evaluate this: ([(:temp x) (:dtof x)])

vectors are callable of course in Clojure but this example is a) syntactically wrong (you're missing an argument in the call) and b) semantically wrong (your intent is not to call a vector but to build it)

Your original attempt: (map #(vec (get % :temp) (get % :dtof)) raw-set))) was also wrong because you need vector instead of vec (`vec` works on a collection but vector is variadic, it builds a vector from its individual elements)

OK, wow, I was wondering, I thought vec == vector, good explanation.

For reference:

user=> (read-string "#([(:temp %) (:dtof %)])")
(fn* [p1__196#] ([(:temp p1__196#) (:dtof p1__196#)]))
user=> (read-string "(fn [m] [(:temp m) (:dtof m)])")
(fn [m] [(:temp m) (:dtof m)])

> OK, wow, I was wondering, I thought vec == vector, good explanation. @U012GN57FJ9 Most IDEs let you see the signature of the function the cursor is at, consider enabling this feature in yours. It's really useful, especially as you're learning the language

-Sforce also results in the same output being generated (ie. referencing old versions that have since been updated)

there's nothing else cached anywhere for your classpath calculation, so I assume it's actually calculating it differently. presuming it's not something in your ~/.clojure/deps.edn, it would be useful to have the deps.edn and Clojure CLI version you're using, and a more precise description of what seems wrong to diagnose

if you can't share the deps.edn, then sharing the -Stree (or -Strace trace.edn) would be a good substitute

I tried using -Srepro to try and rule out the ~/.clojure stuff

DM'ing a few things (can't post publicly, but hoping it helps)

Figured it out, was my fault. Sorry to waste your time.

rubber duck ftw :)