That seems like a subjective decision. I wouldn't, personally, because I don't use Spec as a "type system" -- I use it mostly around the edges of my programs to make sure inputs and outputs of the system conform to expectations. I use it very sparingly inside my program. Other people like to use Spec instrumentation pretty liberally so they're going to give you a different answer.

Yeah like Sean says we have a different approach. We're spec'ing more and more our interfaces. We find it helps us when you haven't seen a piece of code for a while, to figure out what is expected to go in and come out. YMMV.

We're currently depending on 0.2.19-SNAPSHOT so we're testing each new version as a matter of course. Thank you for all the updates and being receptive to rolling the EDN file change back after some folks tried using it. The check/`test` API additions are very nice -- that has enabled us to streamline our build.clj / CI pipeline (we've essentially merged :build and :poly aliases so we can avoid a process creation to run poly commands from our build script).

Sounds great.

It was a little bit of a struggle to get it right this time!

poly+rama+electric yum