This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-06-12
Channels
- # announcements (2)
- # aws-lambda (2)
- # beginners (402)
- # berlin (2)
- # calva (21)
- # cider (8)
- # clj-kondo (31)
- # cljdoc (1)
- # cljsrn (42)
- # clojure (43)
- # clojure-berlin (2)
- # clojure-dev (21)
- # clojure-europe (4)
- # clojure-hamburg (1)
- # clojure-italy (37)
- # clojure-nl (7)
- # clojure-spec (50)
- # clojure-uk (121)
- # clojurescript (46)
- # component (49)
- # data-science (1)
- # datomic (60)
- # emacs (29)
- # fulcro (43)
- # hoplon (5)
- # jackdaw (7)
- # joker (19)
- # luminus (5)
- # off-topic (28)
- # om (2)
- # re-frame (27)
- # reitit (7)
- # remote-jobs (15)
- # rewrite-clj (17)
- # shadow-cljs (95)
- # spacemacs (34)
- # sql (9)
- # tools-deps (17)
- # xtdb (70)
I’d like to maintain a fork of rewrite-clj for clj-kondo, related to this issue: https://github.com/borkdude/clj-kondo/issues/254
considering the radio silence of the maintainer, I think I’ll just go ahead, as I think waiting for his reply can take forever…
I’ll have something eventually @borkdude but am still currently distracted by some cljs work
@lee Oh, I’m not posting this to pressure you. I’m not sure if I will switch to an alternative version of rewrite-clj… I’ll probably strip out only the stuff I need and optimize it, less surprises
I did not think you were pressuring @borkdude! If my version were available without current rewrite-clj bugs, you’d probably use it though, right?
although I’ll probably need features that are too specific for rewrite-clj, like stripping out whitespace at parse time, etc. so I’m not sure
if anything, I’d like to contribute all my changes back to the (actively maintained) original if that was meaningful to anyone