This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-11-20
Channels
- # aleph (12)
- # announcements (7)
- # aws (6)
- # babashka (36)
- # beginners (161)
- # boot (1)
- # calva (6)
- # cider (21)
- # clj-kondo (13)
- # cljs-dev (28)
- # cljsrn (1)
- # clojars (3)
- # clojure (13)
- # clojure-colombia (1)
- # clojure-europe (10)
- # clojure-spec (12)
- # clojure-uk (47)
- # clojuredesign-podcast (2)
- # clojurescript (67)
- # datascript (8)
- # datomic (21)
- # duct (3)
- # emacs (6)
- # events (1)
- # fulcro (6)
- # graalvm (98)
- # jobs (1)
- # kaocha (18)
- # luminus (1)
- # malli (7)
- # off-topic (56)
- # pathom (5)
- # re-frame (18)
- # reagent (3)
- # reitit (9)
- # remote-jobs (3)
- # rewrite-clj (10)
- # ring (1)
- # shadow-cljs (155)
- # spacemacs (2)
- # sql (5)
- # tools-deps (27)
- # vim (86)
- # xtdb (2)
hello everyone
what is the spec for checking file data type ?
Hey Folks, I am learning spec
and need help to understand the registry
parte. They say that it help to avoid name collision, but since we already have namespaces, they aren't enough to avoid that? I don't get to see the real advantage of using ::
in spec declaration. Can someone help me to understand please with example will be wonderful
::keywords are “auto-resolved” to have the current namespace so it’s just a useful tool for succinctly making qualified keywords
They create the exact same result as using :my.ns/keyword so use that if you prefer!
You’ll see them in a lot of examples as it just makes the example shorter
Thank you very much @alexmiller
I think I`ve got the big picture now. When you want to use a spec/def
, first spec
look in the spec-registry
if exist then take from there. Else it create it and store it in the spec-registry
. A very naive description of course hehehe
qualified
unless you are working with existing data, don't want to transform it, and it has unqualified keys