This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-04-17
Channels
- # announcements (1)
- # babashka (94)
- # beginners (76)
- # calva (24)
- # cider (24)
- # clj-kondo (1)
- # cljs-dev (16)
- # cljsrn (45)
- # clojure (135)
- # clojure-europe (9)
- # clojure-france (5)
- # clojure-germany (2)
- # clojure-italy (12)
- # clojure-losangeles (13)
- # clojure-nl (3)
- # clojure-portugal (54)
- # clojure-uk (20)
- # clojurescript (55)
- # conjure (67)
- # core-async (5)
- # cursive (2)
- # datomic (10)
- # docker (7)
- # duct (22)
- # emacs (16)
- # fulcro (34)
- # graalvm (15)
- # hoplon (1)
- # instaparse (1)
- # jobs-discuss (3)
- # juxt (94)
- # luminus (1)
- # meander (4)
- # off-topic (13)
- # pathom (4)
- # pedestal (1)
- # ring (3)
- # ring-swagger (2)
- # shadow-cljs (61)
- # spacemacs (17)
- # specter (2)
- # sql (23)
- # xtdb (33)
hello folks, I’m pleased to announce that Pathom finally has a logo! The repo is updated to show it and more things are on the way, stay tuned!
@wilkerlucio now that I understand planner's foreign-ast, does it make sense to make use of core join (`p/join`) to process recursively the ast? maybe in a separate parser and calling that from the dynamic resolver
or is there any other facility provided by pathom helping with that that I don't know of
@myguidingstar I highly recommend you don’t use p/join
in the middle of your processing, the planner is doing the work to send you only the AST you can answer, and nothing else, so you should process that directly, this is more like what you did on previous walkable version, its ok to use a secondary parser if you want to internally, but using p/join
will trigger all the user extensions as well, and I believe this will generate more overhead than it should