-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
var-info.edn: address TBDs #396
Comments
I'm currently looking through this file because clj-kondo uses it, and it's leading to some false negatives when linting unused values. For example: (do (fn [] 1) 2) doesn't raise any error, because var-info.edn doesn't say anything about clj-kondo should probably mark things with The following macros are marked as clojure.java.jdbc/metadata-query
clojure.core.cache/defcache
clojure.tools.trace/dotrace
clojure.tools.trace/deftrace
clojure.core.async.impl.ioc-macros/gen-plan
clojure.tools.reader/syntax-quote
clojure.core.async.impl.ioc-macros/aset-all! So I guess marking macros as For posterity, here are some other inconsistencies;; (and pure-fn (false? pure-if-fn-args-pure))
clojure.java.jdbc/metadata-query
clojure.tools.trace/trace-compose-throwable
clojure.tools.trace/clone-throwable
clojure.tools.trace/trace-forms
clojure.tools.trace/trace-form
clojure.tools.trace/trace-special-form ;; (and side-effect pure-if-fn-args-pure)
clojure.core/transduce
clojure.core/run! @vemv I'd be interested in making a PR to address some inconsistencies, but want to avoid breaking Eastwood things which I don't know about. There may be good reasons for some vars being marked as |
var-info.edn: has various TBDs.
In addition, there's #236 (comment)
The text was updated successfully, but these errors were encountered: