Fork me on GitHub
Alex Miller (Clojure team)00:05:20

You shouldn’t do that

Alex Miller (Clojure team)00:05:52

But it’s similar to calling s/def with an s/fspec

gfredericks22:05:52 There's a thing here where spec is relying, for no clear reason, on what I'd like to say is a quasi-buggy implementation detail of test.check that I'd like to change. So I'm wondering if actually changing that is realistic, given the alphas and the whatnot. It would mean that the next release of test.check is not compatible with the current releases of spec.alpha. And it's hard to think of how to keep that from being a confusing pain to users who upgrade in the "wrong" order. 😕

Alex Miller (Clojure team)11:05:51

I would greatly prefer this to change in a growth compatible way (new fn if necessary)


there are enough moving parts that I hadn't thought about something like that, but I might be able to make it work; thanks