Clojurians Log v2

This page https://clojurians-log.clojureverse.org/test-check/2019-02-26 and this https://github.com/clojure/test.check/blob/88eebf105fbb01db17ce12a3bff207cc395270b9/src/test/clojure/clojure/test/check/test.cljc#L18 seem to imply that I should be able to use it, but I don't see how

If I try require

[clojure.spec.gen.alpha :as gen :include-macros true :refer-macros [let]]

@borkdude just because of the previous link

It doesn't because let is a macro and can't be lazy loaded (I believe that's the reason anyways). You can use the non-macro version, bind which is part of clojure.spec.gen.alpha

Just to clarify, let is not available in the Clojure version of clojure.spec.gen.alpha either.

@colinkahn if the problem is the lazy loading, can I somehow preload it? Yes, I was trying to use let because it seems cleaner wrt bind and fmap which is what I'm using now. So, are the tutorials outdated? Was let removed from clojure.spec.gen.alpha at some point? I thought I used it in the past 😮

moreover, where is this code https://github.com/clojure/test.check/blob/master/src/test/clojure/clojure/test/check/test.cljc#L1054 getting the gen/let?

ok, I'm so dumb, I should just have imported clojure.test.check.generators where the let macro I'm interested in is actually defined 🤦‍♂️. Thanks for the help!

Those examples look like just test.check, which specs gen namespace lazy load behind statically defined functions. It's a design decision in spec, that all the functions in the gen namespace can be used without loading clojure.test.check.generators until needed (for example people could define specs for use in production code but only incur loading the test.check.generators namespace in their test suite where they'll use that functionality). In ClojureScript, it's the same but there is no true lazy loading, but you only need to manually require the test.check namespaces when you need them.

^ but yeah if you don't care about this stuff then just import test.check generators like you just posted 😊

awesome! Now I understand why the re-export was needed and what's the problem with re-exporting the let macro. Thanks again @colinkahn

after a bit of research, I decided to use metosin/malli. Seems to have all the features I need and I like the data-driven orientation.

Currently spec 2 is a work in progres and not ready for production use, so there is not much to be found, but if you’re still interested to give it a try, there’s some info on the github’s repo wiki (https://github.com/clojure/spec-alpha2/wiki), and the talk where Rich talks about it https://www.youtube.com/watch?v=YR5WdGrpoug&ab_channel=ClojureTV

Spec 2 still has a lot of bugs and has gone through a lot of changes -- with a number of additional changes still planned. We have been very heavy users of Spec (1) since it first dropped -- in production code -- and for about three months we ran a branch of our code tracking Spec 2 but it just became intractable to keep tracking it and working around the bugs...

got it. I will use spec 1 then. thanks.