Fork me on GitHub

it likely is, cider is likely redefing the report function in clojure test with function that is not a multimethod

Alex Miller (Clojure team)02:09:13

Yes this is the lein monkey patching

Alex Miller (Clojure team)02:09:46

There are issues in both lein and test.check about it and it's fixed in test.check master

Alex Miller (Clojure team)02:09:01

You can disable lein monkey patch to avoid

Alex Miller (Clojure team)02:09:15

Well I guess it could be a cider variant of the same problem, not sure


somebody filed a bug report a few months back, I think to test.chuck, wherein I convinced them that cider was monkeypatching the wrong way


it was probably fireplace too


Hello, just a quick question with the new spec system. Where do I place my specs? In the same namespace as the things they specify are declared? And how do I go about making them compatible with older versions of clojure? I am imagining my lib being used in 1.7 and 1.8 as well.


Ah I see there are back ports for spec


Other libs have put the specs in a separate ns so users on older versions can ignore them


meh; stest/check now basically looks like it hangs forever and I don’t know which thing it’s choking on


it’d be nice if there was a debug mode or something where it told me what it was working on


It’s definitely helpful in finding bugs though 🙂


also in making my laptop not very suitable for holding on a lap 😄