This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-10-10
Channels
- # aleph (2)
- # arachne (1)
- # beginners (5)
- # boot (33)
- # cider (12)
- # cljs-dev (6)
- # cljsrn (26)
- # clojure (33)
- # clojure-austin (7)
- # clojure-belgium (6)
- # clojure-chicago (1)
- # clojure-dusseldorf (1)
- # clojure-fr (1)
- # clojure-hamburg (1)
- # clojure-nl (11)
- # clojure-portugal (3)
- # clojure-russia (14)
- # clojure-spec (35)
- # clojure-uk (28)
- # clojurescript (49)
- # component (7)
- # core-async (75)
- # cursive (13)
- # datomic (15)
- # dirac (57)
- # emacs (5)
- # events (1)
- # hoplon (34)
- # jobs (2)
- # jobs-discuss (8)
- # lambdaisland (1)
- # lein-figwheel (7)
- # leiningen (3)
- # om (5)
- # onyx (8)
- # re-frame (56)
- # reagent (13)
- # testing (7)
- # untangled (30)
- # vim (51)
- # yada (17)
@bcbradley maybe this belongs in #core-async
I'm trying to implement a simple filter-map-reduce over a lazy sequence, but in the filter-map operations I only operate over a specific field of the map that comes in the sequence
so I have as sequence of maps like {:a 1 :b 2}
, and the filter-map operations focus only on :a
since this has a lot of filters, I was wondering if there's a method to do this that isn't me doing deep accesses on the maps on each filter-map function
@punnie you could combine all your maps and filters and reduces into one function that you pass to reduce. you could write a function that does the "deep reaching" for you so it's not inconvenient in each of the maps and filters. you could use specter
with filterers and collectors
keep
has the same problem, I think: I'd have to keep the map structure throughout the operation when all I want up until the end is the value of :a
well.. most of the time. I wouldn't use it if I was writing something I want to distribute as a library I guess
Is there a way to do a docstring in a method definition for deftype
or is that limited only to the protocol's definition?
which means @mattly you can add a docstring to the automatic ->Foo
constructor that you get when you (deftype Foo...)
is anyone building the app from jenkins to docker? i’m unsure if there’s an easy automatic way to bump the release version and create a container with the right version, as the jar has the version number appended to it.
as i come from a rails (that we basically checkout and run), i’m a little bit confused in how to integrate all that with our ci..