This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-10-28
Channels
- # aleph (3)
- # beginners (10)
- # boot (135)
- # clara (2)
- # cljsjs (2)
- # cljsrn (1)
- # clojure (68)
- # clojure-austin (4)
- # clojure-france (2)
- # clojure-japan (1)
- # clojure-spec (30)
- # clojure-uk (11)
- # clojurescript (48)
- # component (65)
- # cursive (5)
- # datomic (40)
- # dirac (5)
- # emacs (3)
- # events (16)
- # funcool (2)
- # klipse (46)
- # lein-figwheel (2)
- # luminus (8)
- # off-topic (4)
- # om (7)
- # other-languages (4)
- # parinfer (21)
- # re-frame (15)
- # reagent (30)
- # ring (1)
- # ring-swagger (9)
- # rum (3)
- # specter (7)
- # test-check (8)
- # testing (5)
- # vim (21)
- # yada (4)
@nathanmarz don’t know if this is a silly question or not, but is there any remote chance or plan to have specter become part of clojure.core?
And if not I’d be interested to know if there’s a specific reason why in terms of design philosophy etc.
I’m afraid it works the other way around, there may be no specific reasons why something is not in core. To get something into the core there must be very compelling reasons for it. I mean really compelling. Being a popular/useful/well-maintained/general library is not enough of itself. One such compelling reason I could imagine with specter would be the core library using specter internally, so it would make sense to expose it as well. Similar to clojure.spec. Or another reason could be when specter could not be implemented as a library and would have to be implemented as part of core for some reason… just my $0.02 thoughts
@achesnais @darwin I get that question a lot and I understand why
Specter solves such a fundamental, universal problem that I do believe it makes Clojure much stronger, so in that sense it would make sense to be distributed with the language
ultimately though it's not up to me what goes into core