Yes, that is a major selling point. Generative testing is really cool, and
you should definitely not be disheartened - it's a tool like any other,
with its strong points and weak points (like static typing, too). It's
definitely not universally applicable, and even more than standard testing,
it re
boot-bundle now comes with unit tests and supports first class version
values:
https://github.com/borkdude/boot-bundle/blob/master/README.md#version-values
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@g
Hi all:
I think I encountered a problem in the clojure.core/take produces lazy
sequences, and I wanted to run it by some folks to confirm it was indeed a
bug.
In a nutshell, clojure.core/take produces lazy sequences in a way such that
(take
(count t) t) will always retain the head of its bas
Generative testing is great but defining the contract gets more
complex the further away from a 'unit' you get. It is easy to define
extensive generators for (defn length [s]). It is a much bigger
problem to generate extensive inputs for every call-site of (length)
and then every call-site of the c
