Is it expected behavior that s/valid?
needs the test.check
library and needs to construct a gen for every (nested) spec it's validating against? seems counterintuitive to me, but maybe I'm missing something.
It's only necessary when checking fspec
s.
I'm getting "Unable to construct gen at: ..." errors when calling (s/valid? ::my-spec my-val)
I suspect ::my-spec
uses s/fspec
.
the one it's erroring on currently looks like this: (s/def ::log-file #(instance? File %))
I agree with kenny, that this seems like what you'd see with s/fspec
and generally, s/valid? will not require test.check unless you are gen'ing
hmm... ok. yeah, commenting out my two fdef
's eliminated it. thanks!