This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-09-04
Channels
- # architecture (10)
- # bangalore-clj (2)
- # beginners (2)
- # clara (3)
- # cljs-dev (39)
- # clojars (2)
- # clojure (21)
- # clojure-art (2)
- # clojure-austin (6)
- # clojure-berlin (5)
- # clojure-gamedev (4)
- # clojure-russia (1)
- # clojure-spec (15)
- # clojure-uk (4)
- # clojurescript (4)
- # cursive (3)
- # datomic (1)
- # events (5)
- # flambo (6)
- # hoplon (55)
- # jobs (20)
- # lein-figwheel (2)
- # om (8)
- # onyx (1)
- # pedestal (4)
- # perun (3)
- # protorepl (2)
- # re-frame (8)
- # reagent (48)
- # slack-help (1)
- # specter (5)
- # yada (46)
it likely is, cider is likely redefing the report function in clojure test with function that is not a multimethod
Yes this is the lein monkey patching
There are issues in both lein and test.check about it and it's fixed in test.check master
You can disable lein monkey patch to avoid
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
no nevermind
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