I see this output from kibit:
However taking kibit's advice results in the following compile error:
Can't take value of a macro: #'clojure.tools.logging/warn
I guess the unneeded functions section of misc.clj needs to understand the difference between a function invocation and a macro invocation.
Another problem (similar) is that Java constructs are considered to be first-class functions, which they are not. So kibit currently recommends this:
But this is not correct, because Boolean. is not a function. It must be wrapped in a lambda to be passed around as a function. Similarly java interop calls like .toString are also not functions. So the following examples don't work:
(apply .toString )
(map Boolean. ["true" "false"])
but these do work:
(apply #(.toString %) )
(map #(Boolean. %) ["true" "false"])
This is a fundamental limitation of kibit. I don't think there's a way to work around this but I'd be happy to hear ideas.
@danielcompton, I don't currently follow how the lack of macro expansion (that I think you're referencing from the readme) means that this cannot be solved. Would it not be possible to e.g. change the rule so that any function name that begins or ends with . is not considered eligible for this rule?
Sorry if I've missed what you're getting at here.
Gotcha. We can't cover the general case of all macros but it should be possible to exclude sugared Java interop.