This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-12-30
Channels
- # adventofcode (7)
- # announcements (9)
- # babashka (20)
- # beginners (182)
- # calva (9)
- # cider (20)
- # circleci (3)
- # clj-kondo (1)
- # clojure (269)
- # clojure-europe (2)
- # clojure-india (1)
- # clojure-italy (6)
- # clojure-nl (5)
- # clojure-uk (50)
- # clojurescript (56)
- # code-reviews (3)
- # core-async (174)
- # datomic (4)
- # duct (1)
- # emacs (3)
- # events (1)
- # fulcro (31)
- # graalvm (10)
- # graphql (8)
- # jobs (1)
- # joker (11)
- # juxt (7)
- # luminus (2)
- # malli (4)
- # off-topic (2)
- # overtone (1)
- # pathom (2)
- # re-frame (24)
- # shadow-cljs (42)
- # sql (1)
- # tools-deps (10)
I'm starting to put some time into this. I would love ideas for the project! At the moment I don't think coding help would be useful, since everything is so unstable. Once I have a usable core I'll make a call for help. The readme explains why and what I want make this.
Made a thing to cut out the unused vars from a project: https://github.com/borkdude/carve Typical usage:
clj -A:carve --opts '{:paths ["src" "test"]}'
I remember one day, many months ago, when you didn’t release something :)
So, intriguing but I have to ask - when does the need typically come up? (I’d imagine all sorts of IDEs, lingers and build pipelines would also catch stuff like this?). Thanks 😊
@UCW3QKWKT I'm not using such an IDE myself, but having this as an IDE-independent tool gives more options and having options is nice