This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-06-28
Channels
- # announcements (6)
- # aws (8)
- # bangalore-clj (1)
- # beginners (249)
- # calva (27)
- # cider (5)
- # clara (8)
- # clj-kondo (11)
- # cljs-dev (14)
- # cljsrn (21)
- # clojars (1)
- # clojure (206)
- # clojure-europe (3)
- # clojure-greece (2)
- # clojure-italy (39)
- # clojure-nl (19)
- # clojure-spec (50)
- # clojure-uk (19)
- # clojurescript (31)
- # clojurex (24)
- # community-development (10)
- # core-async (32)
- # core-typed (4)
- # cursive (8)
- # data-science (15)
- # datomic (42)
- # figwheel (1)
- # fulcro (18)
- # graalvm (6)
- # joker (1)
- # kaocha (1)
- # nyc (1)
- # off-topic (1)
- # reagent (5)
- # reitit (2)
- # remote-jobs (2)
- # shadow-cljs (3)
- # spacemacs (2)
- # tools-deps (65)
- # xtdb (3)
'ello 'ello 'ello
morning
Lots of interesting discussions about the #clojurex conference on the #clojurex channel. Would love to hear more thought and feedback
On-topic question. What is the fundamental difference between using doall
followed by prn
vs just doing the prn
:
user=> (def v [:foo :bar :baz])
#'user/v
user=> (->> v (doall) (prn))
[:foo :bar :baz]
nil
user=> (->> v (prn))
[:foo :bar :baz]
nil
user=>
if *print-lenth*
is set, then prn won't traverse the whole structure while printing it
If I'm reading this right, (doall)
forces eager evaluation so the entire data structure gets instantiated in memory.
I thought that was the case.
Saturday's study group broadcast: https://youtu.be/pyIbP4BOGpQ A discussion 4Clojure challenge number 53. I think this is the hardest challenge I have come across, especially to do in a very functional way. I'll walk through a loop/recur approach (it gets a bit long) and then refactor to something a bit more functional.