This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-03-25
Channels
- # announcements (8)
- # aws (50)
- # aws-lambda (6)
- # babashka (25)
- # beginners (119)
- # bristol-clojurians (5)
- # calva (25)
- # chlorine-clover (23)
- # cider (6)
- # cljs-dev (125)
- # clojure (63)
- # clojure-austin (1)
- # clojure-belgium (1)
- # clojure-dev (48)
- # clojure-europe (11)
- # clojure-italy (2)
- # clojure-nl (5)
- # clojure-spec (3)
- # clojure-uk (66)
- # clojurescript (14)
- # core-logic (5)
- # datomic (13)
- # emacs (10)
- # events (2)
- # fulcro (37)
- # graalvm (11)
- # hoplon (95)
- # jobs-discuss (9)
- # juxt (11)
- # kaocha (16)
- # meander (13)
- # off-topic (24)
- # pedestal (4)
- # re-frame (36)
- # reagent (10)
- # reitit (15)
- # ring-swagger (5)
- # shadow-cljs (23)
- # spacemacs (2)
- # sql (13)
- # tools-deps (32)
- # xtdb (11)
I keep working on the assumption that [{:key ?value} …]
is the same as (m/scan {:key ?value})
Sometimes it works and sometimes it doesn’t. What am I not getting? lol
If you look at the docstring of scan you will see it is equal to [_ ... pattern . _ ...]
. So unlike a simple repeat scan can skip over elements.
Ah I see.
I’m starting to grok how this works. With respect to when I read the code lol. Ignore, repeat ignore, match pattern, stop point for next repeats, ignore, repeat ignore.
And gather
which is like filter. I think many places people are using scan
they could use gather
and not use search.
I use cljdoc to look at documentation. Those ones are not in there. Could be due to it failing the build. @U06MDAPTP @U5K8NTHEZ
I'll fix that today. Sorry about that. You can go back one version to look at them.
All good! Appreciate all the work you guys are doing! I couldn’t imagine writing this 120 line meander function for transforming deeply nested json any other way
All fixed
The only problem was the API docs from the doc strings.
I think I was also using it a bit wrong on cljdoc. Also my bad :p