Fork me on GitHub
#clojure-spec
<
2016-11-29
>
mathpunk08:11:37

@alexmiller That's a very helpful example, thank you.

mathpunk08:11:45

@alexmiller @hiredman: As for loading the code that registered them -- I was missing that using ::foo expands to the whole namespace name i.e. including the name of the app. The 'fully' in fully qualified 🙂

nwjsmith14:11:39

Are there plans to dynaload the shuffle combinator from test.check?

nwjsmith14:11:26

Would a patch be welcome for such a change?

alexmiller14:11:57

I think there’s actually a pending patch that has that included in it

alexmiller14:11:07

but yes, would be happy to add it

nwjsmith14:11:31

starts digging through Jira to upvote

alexmiller14:11:39

which is ready for Rich to look at so I expect that will happen whenever he’s looking at tickets next

nwjsmith14:11:47

Excellent, thanks Alex

bbloom20:11:48

create-ns and alias seem relatively useful for spec, but clojurescript doesn’t really support these - any good alternative other than verbose keywords?

alexmiller20:11:00

prob best to ask this in #clojurescript or #cljs-dev

dnolen20:11:17

@alexmiller I think this is good argument for :alias at the ns form

dnolen20:11:20

it’s already come up before

dnolen20:11:39

and I believe continued usage of clojure.spec will drive the desire for such a feature

alexmiller20:11:17

well you’re talking to the wrong person :)

jfntn23:11:56

Is there a way to add meta data to spec definitions without re-implementing s/def?

hiredman23:11:51

specs are "named" by symbols (which can have metadata attached) and keywords (which cannot)

hiredman23:11:53

but symbols are not interned, so given a symbol 'a if you associated some metadata, another instance of that symbol will not have that metadata

hiredman23:11:27

by that I mean, even if you did re-implement s/def you would have a hard time putting metadata somewhere

alexmiller23:11:32

The answer is no (for now) but it would be useful to have at least a doc string and I'd say that's still a possibility

alexmiller23:11:59

As hiredman mentioned, the tricky part is where to put it

alexmiller23:11:21

There are some options but none that are obviously good