This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-05-31
Channels
- # aleph (3)
- # aws (5)
- # beginners (65)
- # boot (17)
- # cljs-dev (112)
- # cljsrn (5)
- # clojure (146)
- # clojure-austin (3)
- # clojure-dusseldorf (3)
- # clojure-italy (18)
- # clojure-norway (13)
- # clojure-russia (84)
- # clojure-serbia (5)
- # clojure-spec (24)
- # clojure-uk (84)
- # clojurescript (204)
- # css (1)
- # cursive (21)
- # data-science (3)
- # datascript (21)
- # datomic (26)
- # emacs (5)
- # euroclojure (1)
- # hoplon (8)
- # jobs (7)
- # jobs-discuss (2)
- # keechma (35)
- # lumo (92)
- # mount (1)
- # nrepl (2)
- # numerical-computing (16)
- # off-topic (10)
- # om (58)
- # re-frame (13)
- # reagent (90)
- # remote-jobs (2)
- # ring-swagger (1)
- # spacemacs (9)
- # specter (6)
- # unrepl (17)
- # untangled (56)
- # yada (2)
@otfrom there's no reason that reducers couldn't be made to work as arguments to c.c.m.dataset
API functions. And then you could use transducers as usual. If there's a use case, happy to consider.
The idea of clojure.core.matrix.dataset
is similar to the main clojure.core.matrix
API: we provide a set of useful and general purpose API functions that can be supported by multiple implementations (e.g. you can have data tables from spark, JDBC result sets, Clojure data structures etc.)
@mikera I'd never thought of using transducers on a c.c.m.dataset w/out changing it to a row-seq first. I'll have a look at the API again and see if I can figure out how to get a reducer in there (cc @elise_huard)