hi all!

do we have any means of specifying records?

s/keys should just work on them

thanks!

Whats the best way to test a spec'd function that has side effects?

@guy I’m not sure about the best way, but mocking can help speed things along if that’s what you’re after. https://github.com/benrady/specific

Thanks @jaymartin have you tried it with the latest version of clojure.spec.alpha (17) ?

it looks like specific is using alpha13

No, I’ve just messed about with it playfully. But the ideas should be rather generic.

kk thanks :thumbsup:

Is there an equivalent of declare for specs?

alternatively, is there a way to disable the check to see if a spec name exists when used in other specs?

basically I would like to structure my code in the following order:

(s/def ::x ::y)
(s/def ::y ...)

replacing the first ::y with (s/and ::y) seems to work.

feels kinda odd that it doesn't just work, seeing as most of things in spec are lazy evaluated

@aengelberg what do you mean

@guy he means

boot.user=> (s/def ::foo ::bar)
clojure.lang.Compiler$CompilerException: java.lang.Exception: Unable to resolve spec: :boot.user/bar, compiling:(boot.user1422927036988753503.clj:1:1)

Sorry im probably being slow

he wants to use a different spec and call it something new?

he wants to say that the spec for ::foo is the same as the spec for ::bar, and it be ok that the spec ::bar has not been defined yet

@aengelberg when I've wanted that I've just used (s/def ::bar any?)