This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-12-08
Channels
- # adventofcode (31)
- # beginners (97)
- # bigdata (2)
- # boot (276)
- # cider (17)
- # cljsrn (5)
- # clojure (150)
- # clojure-china (3)
- # clojure-conj (8)
- # clojure-greece (1)
- # clojure-india (1)
- # clojure-korea (1)
- # clojure-new-zealand (4)
- # clojure-russia (40)
- # clojure-spec (119)
- # clojure-uk (116)
- # clojurescript (87)
- # code-reviews (110)
- # core-async (4)
- # cursive (11)
- # datomic (26)
- # garden (4)
- # gorilla (7)
- # hoplon (82)
- # humor (1)
- # jobs (2)
- # jobs-discuss (10)
- # luminus (17)
- # onyx (60)
- # planck (2)
- # play-clj (2)
- # protorepl (70)
- # re-frame (121)
- # reagent (7)
- # ring-swagger (3)
- # rum (16)
- # test-check (16)
- # untangled (12)
- # yada (20)
@martinklepsch is there a typo in the changelog? (let [{:keys [:product/text]} (d/react-all state)]
@kauko: what specifically are you referring to?
I don't think so. I briefly checked the destructing docs on http://clojure.org but basically you cannot have namespaced local bindings
So you pass a keyword and there will be a binding for the part after the /
I could be wrong though, it's certainly something I haven't used extensively
Yeah i think it was acciental though that the destructing works by using a keyword, it should be {:keys [product/test]}
technically
@rauh: all (?) examples here show the keyword syntax http://clojure.org/guides/destructuring
That nice snippet doesn't allow multiple bindings somehow does it?
Ah ok no I get it now
You can namespace the usual :keys
thing which will then look up keys with the same namespace - cool! 👌🎉