This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-01-10
Channels
- # babashka (17)
- # beginners (57)
- # calva (19)
- # cider (1)
- # clj-kondo (21)
- # clojure (36)
- # clojure-austin (15)
- # clojure-australia (1)
- # clojure-china (1)
- # clojure-europe (35)
- # clojure-filipino (1)
- # clojure-hk (1)
- # clojure-indonesia (1)
- # clojure-japan (1)
- # clojure-korea (2)
- # clojure-my (1)
- # clojure-nl (1)
- # clojure-norway (5)
- # clojure-sg (1)
- # clojure-spec (6)
- # clojure-taiwan (1)
- # clojure-uk (3)
- # clojurescript (7)
- # clr (9)
- # community-development (5)
- # cursive (14)
- # datalevin (1)
- # emacs (5)
- # events (5)
- # exercism (2)
- # figwheel-main (2)
- # fulcro (6)
- # funcool (3)
- # introduce-yourself (2)
- # joyride (7)
- # leiningen (4)
- # london-clojurians (9)
- # malli (3)
- # membrane (1)
- # missionary (54)
- # music (1)
- # nbb (2)
- # pathom (5)
- # pedestal (55)
- # rdf (13)
- # re-frame (10)
- # reitit (3)
- # shadow-cljs (17)
- # vim (58)
- # web-security (12)
What's the reasoning behind cljs.core/uuid
?
It doesn't seem very meaningful, and there isn't one in Clojure core.
Example:
#uuid"foo"
Invalid UUID string: foo
(uuid "foo")
=> #uuid"foo" ;; wth?
maybe a docstring could clean up any confusion, but I don't see an issue with both of these existing.
👍 2
I guess (uuid "foo")
is similar to (keyword "this doesn't looks like a keyword")
. and (symbol "doesn't seem like a symbol")
.
One possibility is (uuid "foo")
gives forward compatibility with future uuid layouts/formats/sizes etc.
As it's part of the core library and it's not actively doing harm. I don't see why it would get deprecated (as deprecation would creates unnecessary uncertainty for all the code/projects using it).