This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-05-14
Channels
- # beginners (19)
- # boot (28)
- # cider (1)
- # cljs-dev (12)
- # cljsrn (1)
- # clojure (246)
- # clojure-belgium (4)
- # clojure-berlin (1)
- # clojure-france (4)
- # clojure-italy (7)
- # clojure-russia (11)
- # clojure-serbia (3)
- # clojure-spec (5)
- # clojurescript (106)
- # cursive (4)
- # datomic (7)
- # emacs (1)
- # jobs (6)
- # leiningen (3)
- # luminus (1)
- # lumo (11)
- # off-topic (1)
- # om (7)
- # onyx (1)
- # pedestal (6)
- # re-frame (16)
- # reagent (4)
- # rum (3)
- # spacemacs (1)
- # unrepl (1)
- # untangled (5)
- # vim (1)
@john just a source code comment indeed. although I could probably use meta for something that stays with the code.
mmm, isn't there a shorthand to add meta docs? Not sure if that'd clobber any metadata though
@matan there's no point on metadata inside a let, because nothing can access the metadata. And let bindings aren't reified like vars so they can't hold metadata in the general case
@matan you can write a macro where it allows a doc string, but who would ever be able to access the doc string?
unless you replace let entirely, you can't put metadata on a in (let [a 1] a) - numbers can never take metadata
could wrap the whole fn in a MetaFn. pull out all the docs on all the lets and put them in the MetaFn's meta. Sounds way hard though.
has anyone had a problem where midje :autotest
runs the first test and after any changes it displays only no facts were checked
?
@vitruvia I’ve seen that happen when the tests aren’t name consistently based on the namespaces they test
Thanks verma. I'm using tests written by someone else so I'm not sure. I'll check them later
here’s a section on how tests are resolved: https://github.com/marick/Midje/wiki/Autotest