This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-11-16
Channels
- # aleph (1)
- # aws (1)
- # beginners (23)
- # boot (33)
- # cider (15)
- # cljs-dev (4)
- # clojure (73)
- # clojure-dev (18)
- # clojure-italy (8)
- # clojure-russia (7)
- # clojure-serbia (1)
- # clojure-spec (8)
- # clojure-uk (118)
- # clojure-ukraine (3)
- # clojurescript (34)
- # code-art (1)
- # community-development (24)
- # cursive (21)
- # data-science (3)
- # datomic (72)
- # defnpodcast (1)
- # fulcro (77)
- # graphql (4)
- # hoplon (8)
- # jobs (3)
- # luminus (3)
- # lumo (7)
- # off-topic (3)
- # onyx (17)
- # other-languages (7)
- # pedestal (1)
- # perun (1)
- # protorepl (21)
- # re-frame (91)
- # ring (4)
- # ring-swagger (18)
- # shadow-cljs (22)
- # spacemacs (37)
- # specter (1)
- # sql (23)
- # test-check (4)
- # unrepl (29)
- # utah-clojurians (3)
- # vim (36)
- # yada (10)
any particular reason why IPersistentSet
has its own get(Object)
and doesn't implement ILookup
?
IPersistentSet almost certainly pre-dates ILookup (which was added later)
is IPersistentSet.get()
really the same intent as ILookup.valAt()
?
this comes from a discussion over #clojure-uk where i was explaining why it doesnt make sense for sets to be IAssociative
, but I was quite surprised to find out that they weren't ILookup
if there's no good semantical reason (and I can't think of one!) for IPS to be an ILookup i'd be tempted to make an enhancement ticket
adding ILookup to IPersistentSet would be a breaking change for existing (non-core) impls of IPS
could be added to Set impls though
that would theoretically make calls to sets of keywords faster?
no, I meant on get