Re: Clojure spec screencast: Testing

Sweet. Looking forward to it. Enjoying the casts so far very quick ramp up. Nice work On Wednesday, July 27, 2016 at 11:52:36 AM UTC-7, stuart@gmail.com wrote: > > Yes. Short answer: Make a model of the input space. Coming in a future > screencast. :-) > > Stu > > On Wed, Jul 27, 2016 at 2

Re: Obtaining the call graph of a clojure project

This is a slightly adjacent issue, but you can see namespace usage ordering with lein-ns-dep-graph . On Thu, Jul 28, 2016 at 11:42 AM Gary Fredericks wrote: > I have a very hacky bunch of code here >

Re: Obtaining the call graph of a clojure project

I have a very hacky bunch of code here that uses tools.analyzer to try to do this. It works okay and I would love for somebody to make it better. On Wednesday, July 27, 2016 at 5:51:03 P

Obtaining the call graph of a clojure project

Hi, Is it possible to get information about the call graph of a project from the clojure compiler? For example in Scala, one can use a compiler plugin, to tap into the AST. This in turn permits deriving more or less the entire call graph of the project, directly through the compiler, rather tha

Can we provide examples in fdef?

Hi All, Not sure if this is helpful or taking it too far, but often when I write a function, I have a few typical happy and unhappy code paths in mind. It would be nice if we can put that into spec's fdef. For example, in addition to :fn, :ret, :args, we add :examples, which is just array of

Re: Clojure spec screencast: Testing

These screencasts are great, Thanks for making them; and of course working on clojure & clojure.spec! :-) R. On 27 July 2016 at 19:52, Stuart Halloway wrote: > Yes. Short answer: Make a model of the input space. Coming in a future > screencast. :-) > > Stu > > On Wed, Jul 27, 2016 at 2:13 PM,

Re: Clojure spec screencast: Testing

Yes. Short answer: Make a model of the input space. Coming in a future screencast. :-) Stu On Wed, Jul 27, 2016 at 2:13 PM, Beau Fabry wrote: > With the passing test of `my-index-of`, is there any way to be confident > that test.check generated inputs that checked the branch of the :fn spec >

cautious wrapper for letfn that does macroexpansion on fnspecs first

letfn assumes fnspecs are all already properly shaped, like: (fn-name [args] body) But it is possible that a macroexpansion is needed to get them in the right shape before letfn does its work, especially if the user found all his fnspecs were of similar shape and used a macro to eliminate boile

Re: Clojure spec screencast: Testing

With the passing test of `my-index-of`, is there any way to be confident that test.check generated inputs that checked the branch of the :fn spec where a return other than nil happened? All of the invocations of `exercise-fn` in the screencast only managed to get nil as a result. On Wednesday,

Clojure spec screencast: Testing

Check out the 2nd screencast about spec, this time on testing with check and instrument: http://blog.cognitect.com/blog/2016/7/26/clojure-spec-screencast-testing -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to cl

Free webinar - Deep Learning: Clojure

Every language has many pre-defined core functions, so we can quickly get on building what we really want. This ease of use does come at a cost, though. Do we really know the power of the magic that we are wielding? In this webinar we will look at how to learn a language by implementing models

Re: Amazonica and S3

Thanks to a quick turn around by the mcohen01, the author, two bugs have been fixed with the bucket notifications and tagging :) The project docs (README) have been updated with examples. On Friday, 22 July 2016 02:24:45 UTC+1, Andrea Richiardi wrote: > > I am glad you solved and raised the issu