@donaldball I think maybe @gfredericks did?

@jfntn not sure

@alexmiller the workaround was to move the self spec before the parent

hmm, fails on Clojure too - I think this is related to a couple other existing tickets where s/def chases the spec too early

I wrote a defn macro that dispatches on specs matching; it didn't make an fdef

hello people, I wanna share with you a snippet that I wrote here to find bad generators on your project, it's helping me a lot (specially when you have a s/keys filled with items and don't know which of then is not generating)

(let [keys (->> (s/registry)
                keys
                (filter #(and (qualified-keyword? %)
                              (not (contains? #{"clojure.core.specs.alpha"
                                                "clojure.spec.alpha"} (namespace %))))))]
  (doseq [k keys]
    (try
      (doall (s/exercise k))
      (catch Exception e
        (println "Bad generator for" (pr-str k))))))

this will print Bad generator for :some/key for the generators that are not being able to find a value after 100 tries

I hope it may help you as it is helping me 🙂

cool!

I'm having an issue generating date-ranges, getting

clojure.test.check.rose_tree.RoseTree cannot be cast to
   clojure.test.check.rose_tree.RoseTree

looks like an AOT compilation problem ^

it's in cljc

is that something that could be causing it?

no -- it has to do with whether you have superfluous *.class files present, and whether you've require/reloaded stuff

okay, then it might be because I hotloaded

calling @hiredman batsignal

let me check that, thanks

reloading things will redefine some classes. Those classes will have the same name as existing classes, but will be != from the JVM's perspective

makes sense

thus instances of RoseTree(1) are not instances of RoseTree(2)

hmmm?

aot drowns kittens in a sack in the river (the kittens are a metaphor for your hopes and deams)

hmm, now I'm running into issues with clj-time.format not being found.

Which the .coerce namespace depends on, which is weird because when I used the function before I restarted it worked.

It's really the only kitten that sometimes needs to claw itself to fresh air once in a while.

(metaphor for the only thing that sometimes gets to me with cljx)

you're using cljx?

@bbss

@ghadi is that not short for clojure(script) ?

Oh right, it's the pre-conditional reader library

there was an earlier library called cljx that did something similar to cljc

sorry, it's cljc

I meant to say, the only thing that I find really annoying at times is dependency issues like these. It takes by far the most of my time out of all time-taking things that aren't normal debugging/coding.

lein clean and lein deps solved it

thanks for saving my kittens 🙂

For folks doing programmatic decoding of explain-data to produce nice messages, it seems that required keys now (in 0.1.123) produce a :pred of (clojure.core/fn [%] (contains? % :the-key)) whereas they used to produce (contains? % :the-key) — this broke a lot of our decoding logic so I figured I’d mention it here in case it helps other debug similar breakage…

given an (s/keys :opt-un [::foo]), what is the best way to generate a map with foo always in it? I occasionally see test failures in CI Couldn't satisfy such-that predicate after 10 tries, when I do (gen/such-that :foo (s/gen ::the-map))