Any chance that the upcoming work on spec1 will include the work spec2 did on making spec objects more accessible/concrete?
https://clojurians.slack.com/archives/C06MAR553/p1795010292465719 I had to use reflection in practice for this, because of people doing naughty things like (s/def ::foo (into #{} [1 2 3])) which was annoying and I expect harms performance in constructing the generator.
No, I think spec2 will not see any further work
The idea from spec2 will not be backported to spec1? That's a shame, it has great utility for things like specs via functions etc
As someone who tracked Spec 2 dev at work for about six months, on a parallel branch to our main deployment, it was quite a disruptive change in some cases, and the programmatic Spec stuff could be hard to use, as I recall. Sorry for lack of details but it was a long time ago (and I don’t think we kept the branch around). We kind of gave up after about six months. I agree that the composition aspect could be valuable tho’.
spec2 is significantly different and still had some big undone work. will some ideas from spec2 eventually make their way to spec1? maybe