This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-07-02
Channels
- # aws (2)
- # babashka (24)
- # beginners (104)
- # calva (1)
- # cider (6)
- # clojure (7)
- # clojure-conj (4)
- # clojure-europe (21)
- # clojure-nl (2)
- # clojure-norway (69)
- # clojure-sweden (1)
- # clojure-uk (4)
- # clojurescript (19)
- # clr (4)
- # core-typed (1)
- # cursive (52)
- # datahike (1)
- # datalevin (7)
- # datomic (8)
- # docker (8)
- # humbleui (22)
- # hyperfiddle (4)
- # jobs-discuss (3)
- # leiningen (1)
- # off-topic (37)
- # pathom (4)
- # polylith (12)
- # remote-jobs (5)
- # vim (4)
- # yamlscript (3)
I don't know if this is the right place to ask, but why is renaming a symbol with clj-refactor so unusably slow? My project is like 1000 lines, and after 2 minutes I got tired of waiting for it to analyze my project. I might have an old version, though. Is there a way to make it faster? Maybe I'm doing something stupid.
I might have an old version, thoughYou should start from there 😄 modern versions have misc parallelism and caching. Although for the analysis phase, most likely it hasn't changed much. The reason for this performance is that we use https://github.com/clojure/tools.analyzer - it is what it is. However once the cache is built. Subsequent usages are cached or incrementally computed.
tbh nowadays I don't use that specific part of clj-refactor / refactor-nrepl. I don't use LSP either which is known to perform well.
With modern naming (no refers, https://stuartsierra.com/2015/05/10/clojure-namespace-aliases :as
prefixes) search/replace can be done by sed or the like