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

@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 🙂

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

Would a patch be welcome for such a change?

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

but yes, would be happy to add it

starts digging through Jira to upvote

yeah, it’s in http://dev.clojure.org/jira/browse/CLJ-2046

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

Excellent, thanks Alex

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

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

ok

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

it’s already come up before

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

well you’re talking to the wrong person :)

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

metadata?

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

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

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

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

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

There are some options but none that are obviously good