This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-02-10
Channels
- # announcements (6)
- # babashka (38)
- # beginners (85)
- # biff (3)
- # calva (2)
- # cider (11)
- # clerk (14)
- # clj-kondo (6)
- # clj-on-windows (27)
- # clj-together (2)
- # cljsrn (18)
- # clojure (106)
- # clojure-austin (1)
- # clojure-belgium (1)
- # clojure-europe (19)
- # clojure-nl (1)
- # clojure-norway (9)
- # clojure-uk (2)
- # clr (2)
- # cryogen (1)
- # cursive (10)
- # datahike (3)
- # datavis (2)
- # datomic (15)
- # emacs (7)
- # graalvm (10)
- # graphql (20)
- # gratitude (1)
- # hyperfiddle (1)
- # improve-getting-started (23)
- # joyride (24)
- # london-clojurians (1)
- # lsp (22)
- # malli (4)
- # matcher-combinators (3)
- # membrane (13)
- # off-topic (1)
- # pathom (24)
- # polylith (9)
- # react (31)
- # reagent (9)
- # releases (1)
- # remote-jobs (1)
- # reveal (3)
- # shadow-cljs (50)
- # spacemacs (3)
- # specter (5)
- # xtdb (5)
Related/follow-up: clj-kondo.impl.rewrite-clj.parser/parse-string
doesn't seem to parse anonymous functions in a way that notes they're functions:
; eval (current-form): (p/parse-string "#(+ 1 %)")
{:children
({:value +, :string-value "+"}
{:value 1, :string-value "1"}
{:value %, :string-value "%"})}
is that intentional? is there another method for parsing input that clj-kondo uses? i'm not sure exactly how it determines what's an anonymous functionHow is this different from normal rewrite-clj? What is the background of your question?
i'm using clj-kondo's parser directly because i'm writing an s-expression pattern matching library for use with clj-kondo
oh interesting. thanks