This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-05-13
Channels
- # admin-announcements (17)
- # aleph (1)
- # arachne (2)
- # boot (152)
- # braveandtrue (8)
- # cljs-dev (12)
- # cljsjs (3)
- # cljsrn (1)
- # clojure (105)
- # clojure-austin (1)
- # clojure-belgium (5)
- # clojure-berlin (1)
- # clojure-brasil (5)
- # clojure-canada (2)
- # clojure-dev (6)
- # clojure-gamedev (1)
- # clojure-greece (9)
- # clojure-russia (39)
- # clojure-uk (9)
- # clojurescript (106)
- # component (4)
- # cursive (1)
- # data-science (3)
- # datascript (1)
- # datomic (9)
- # emacs (6)
- # hoplon (92)
- # jobs (1)
- # ldnproclodo (2)
- # lein-figwheel (1)
- # off-topic (19)
- # om (47)
- # om-next (1)
- # onyx (10)
- # other-languages (1)
- # proton (1)
- # re-frame (5)
- # reagent (36)
- # rethinkdb (1)
- # ring (2)
- # rum (1)
- # yada (14)
It seems to me that update-in is broken for empty paths in the following way: - (update-in {1 2} [] (constantly 3)) currently returns {1 2 nil 3} - I would expect it to return the number 3 Is this by design? If not, is this something that could still be changed?
if I recall correctly, the answer I have seen given in the past with regards to this is that the behavior of update-in with an empty path is undefined
if you search jira for update-in there is a whole list of stuff, http://dev.clojure.org/jira/browse/CLJ-1623 might be a good place to start reading
as much as a loath style guides and the like, it might be nice to add some stuff about record usage to http://dev.clojure.org/display/community/Library+Coding+Standards like "use the factory functions" and "never import the record class unless you also require the namespace where it is defined"