Fork me on GitHub
#beginners
<
2017-05-14
>
matan00:05:42

@john just a source code comment indeed. although I could probably use meta for something that stays with the code.

matan00:05:03

it's just rather ugly compared to how we can add a docstring to a function

john00:05:31

mmm, isn't there a shorthand to add meta docs? Not sure if that'd clobber any metadata though

noisesmith01:05:51

@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

matan01:05:13

anyway docstrings on let variables could have been nice ๐Ÿ™‚

matan01:05:26

yeah yeah I can write a macro ...

john02:05:14

get out of #beginners with that macro talk ๐Ÿ˜‰

noisesmith02:05:15

@matan you can write a macro where it allows a doc string, but who would ever be able to access the doc string?

noisesmith02:05:38

unless you replace let entirely, you can't put metadata on a in (let [a 1] a) - numbers can never take metadata

john02:05:41

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.

john02:05:44

I didn't know let bindings couldn't hold metadata. thanks for that intel ๐Ÿ’ก

vitruvia17:05:19

has anyone had a problem where midje :autotest runs the first test and after any changes it displays only no facts were checked?

verma20:05:33

@vitruvia Iโ€™ve seen that happen when the tests arenโ€™t name consistently based on the namespaces they test

vitruvia20:05:17

Thanks verma. I'm using tests written by someone else so I'm not sure. I'll check them later

verma20:05:46

hereโ€™s a section on how tests are resolved: https://github.com/marick/Midje/wiki/Autotest

vitruvia20:05:48

Thanks it looks really nice and to the point. I'll read them once I'm done with this paper I'm writing =]

verma20:05:58

๐Ÿ‘