@alexmiller in the clojure spec workshop you said you wouldnt use constantly with with-gen in this example:

(def id-gen
  (gen/fmap #(str "ID-" %)
    (s/gen (s/int-in 100000 999999))))

(s/def ::id
  (s/with-gen (s/and string? #(re-matches id-regex %))
    (constantly id-gen)))

ugh, i shouldn't ping ppl at 8pm on sunday. got excited.

@drewverlee It's OK to be excited at weekends 🙂 Just needs to be tempered with a little patience until most folks get to their desks on Monday morning 🙂

Issues with : Call to clojure.core/let did not conform to spec: In: [0] val: () fails spec: :clojure.core.specs.alpha/bindings at: [:args :bindings :init-expr] predicate: any?, Insufficient input - Should I be using clojure.spec or clojure.spec.alpha in my namespace?

Thanks - but ...why am I seeing this error?

I am using spec as a parser, and have just noticed that when I parse a seq with 40 entries (all already realized in memory) I get out of memory errors, any ideas how to avoid this?

seems weird, lots of alternates?

2 alternates with 2 and 4 cases

I haven't played with changing how the spec is structured yet to see if that improves things

I do use s/& a few times, which I can imagine being expensive for backtracking

@hiredman any way you can file an issue?

maybe

don’t know that I can help without a repro case or more info

Any idea how you can get the keys from a spec?

(s/def ::foo (s/cat :name ::name))

(??? ::foo)
=> [:name]

@drewverlee there's a few different options. s/form will give you the spec definition as data that you could walk

Spec form specs will eventually make this easier to answer (see clj-2112)

while I was fiddling with coming up with a minimal test case, I realized I could change the format slightly to have an explicit delimiter instead of an (s/& ...) check, which seems to have solved my performance issues