This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-02-08
Channels
- # aleph (5)
- # announcements (3)
- # aws-lambda (16)
- # babashka (17)
- # beginners (59)
- # calva (168)
- # clerk (4)
- # clj-kondo (62)
- # clojure (77)
- # clojure-belgium (4)
- # clojure-brasil (10)
- # clojure-ecuador (3)
- # clojure-europe (41)
- # clojure-losangeles (2)
- # clojure-nl (2)
- # clojure-norway (24)
- # clojure-uk (2)
- # clojurescript (44)
- # clr (21)
- # community-development (7)
- # conjure (1)
- # cursive (3)
- # datalevin (15)
- # datomic (1)
- # deps-new (12)
- # emacs (45)
- # events (1)
- # fulcro (8)
- # funcool (7)
- # graphql (5)
- # hugsql (15)
- # jobs (2)
- # matcher-combinators (17)
- # meander (14)
- # membrane (31)
- # pathom (28)
- # pedestal (6)
- # practicalli (6)
- # re-frame (12)
- # releases (1)
- # remote-jobs (1)
- # shadow-cljs (32)
- # tools-deps (8)
- # vim (16)
(match [1]
[!x ...] (subst [(+ 1 !x) ...])) ;; => [(+ 1 1)]
is it possible to get this to return [2] using subst?doing something else, but trying to simplify the example to focus on my issue
doesn't work since it's a memory variable in my example.
(match [1 2 3]
[!x ...] (subst [(+ 1 !x) ...]))
m/app might be what I'm looking for
(match [1 2 3]
[!x ...] (subst [(app (partial + 1) !x) ...]))
;; => [2 3 4]
👍why cant unqoute work with memory variables?
I’m not sure of the limitations, but I do know that unquote-splice is a known thing that doesn’t work
could be. my understanding of meander is pretty surface level at the moment
my current workaround
(match [1]
[!x ...] (mapv #(+ 1 %) !x)) ;; => [2]