This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-11-10
Channels
- # announcements (4)
- # asami (3)
- # babashka (49)
- # beginners (56)
- # chlorine-clover (42)
- # cider (13)
- # clara (3)
- # cljfx (14)
- # clojure (65)
- # clojure-australia (2)
- # clojure-dev (12)
- # clojure-europe (57)
- # clojure-italy (10)
- # clojure-nl (3)
- # clojure-spec (25)
- # clojure-uk (25)
- # clojuredesign-podcast (11)
- # clojurescript (78)
- # code-reviews (16)
- # community-development (3)
- # cursive (14)
- # datomic (16)
- # depstar (20)
- # emacs (3)
- # figwheel-main (2)
- # fulcro (33)
- # helix (16)
- # jackdaw (15)
- # kaocha (13)
- # leiningen (3)
- # malli (33)
- # reveal (10)
- # shadow-cljs (29)
- # spacemacs (10)
- # sql (13)
I found it a bit odd that the 2-arity version of keyword
fails on anything else than strings. Now that simple-symbol?
and simple-keyword?
exist to validate the input, could it relax its input requirement for these two cases? (Granted: this is a very minor oddity, just wondering for my own curiosity)
Relax to support what? Symbols and keywords?
Is there some example where this would be useful?
Is this a case of Hyrum's law or is this really supported on purpose? https://github.com/borkdude/sci/issues/440
I'm not sure, but as an extra datapoint, deftype
ignores the namespace segment aswell, and I'm 100% sure somewhere in clojure.core
there's code that emits deftypes with clojure.core namespacing (on interface method names)
(e.g. it macroexpands to
(deftype* user/x user.x [...] :implements [... ] (clojure.core/entrySet [..] ...) ..)
)