Fork me on GitHub
#clojure-spec
<
2017-11-20
>
qqq05:11:42

they very act of writing specs is making my code clearer

qqq05:11:54

it's forcing me to think: what condition does this key have to satisfy to be valid, and documenting it as code

qqq07:11:47

this is kind of insane, but is there a way to (while only holding weak references), tell clj/cljs to memoize calls to (s/assert SPEC OBJ) ?

gfredericks12:11:08

the jvm has a hashmap for that sort of use case I think dunno how easy monkeypatching s/assert to get that effect would be

gfredericks12:11:27

why're you calling multiple times?

johanatan20:11:39

are there any known gotchas involving partial application around a stest/instrumented function ?

hiredman21:11:00

it depends what you mean

hiredman21:11:59

instrument works by setting the root value of vars to an instrumented value of the function, but if you have already taken the value of a var before instrumenting, of course that will have effect

hiredman21:11:44

so if you have something like (def f (partial g 1)) and then later instrument, calling f won't call the instrumented version of g