This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-09-08
Channels
- # aws (21)
- # beginners (62)
- # boot (29)
- # chestnut (1)
- # cider (110)
- # cljs-dev (37)
- # clojure (93)
- # clojure-berlin (1)
- # clojure-dev (10)
- # clojure-greece (4)
- # clojure-italy (5)
- # clojure-new-zealand (1)
- # clojure-spec (6)
- # clojure-uk (46)
- # clojurebridge (1)
- # clojurescript (54)
- # cryogen (1)
- # cursive (22)
- # datomic (72)
- # emacs (2)
- # events (3)
- # flambo (1)
- # hoplon (88)
- # jobs (6)
- # juxt (51)
- # lein-figwheel (1)
- # leiningen (3)
- # lumo (12)
- # mount (4)
- # off-topic (3)
- # onyx (3)
- # pedestal (4)
- # portkey (27)
- # re-frame (13)
- # reagent (1)
- # ring (4)
- # rum (2)
- # uncomplicate (1)
- # unrepl (3)
@alexmiller looks like the Jira is getting spam’d https://dev.clojure.org/jira/browse/CLJS-150
fixed, thx
have better more informative names for IAtom2 been considered? IAtomVals or something to that effect (like IReduceInit)
other names were considered yes
the idea is that it is an extension of the original interface
ok, follow up question: any particular reason why this couldn't be implemented on top of compare-and-set rather than requiring an interface? seems a bit odd
maybe? if you can cover the validate and watch requirements w/o putting it in Atom, then file a ticket