Clojure Q&A - Recent questions tagged tools.analyzer

Sub-optimal coding technique in clojure.tools.analyzer.utils ?

Fri, 26 May 2023 13:23:58 +0000

Nearly nine years ago, when making tools.analyzer cross-platform (JVM/CLR), we did not yet have reader conditionalization. Leading to this bit of inelegance:

https://github.com/clojure/tools.analyzer/blob/726ab4f085f00c1c03f564dec359d50362efc846/src/main/clojure/clojure/tools/analyzer/utils.clj#LL81C1-L95C1

The commit actually has the comment "until we have feature expressions".

(- Since there needs to be question -): Isn't time to get rid ourselves of the affliction of throwing an exception to detect the platform and convert to reader conditionalization?

If there is Jira issue, I can submit a patch.

`Ambiguous method signature for method: close` thrown where clojure.core wouldn't

Thu, 01 Apr 2021 17:15:51 +0000

The following code will throw an exception:

(ana.jvm/analyze '(reify
                    java.io.Closeable
                    (close [_])
                    example.foo/EventClient
                    (close [_])))
                    ;; => clojure.lang.ExceptionInfo: Ambiguous method signature for method: close

...where example.foo/EventClient is a a real, resolvable defprotocol that does in fact define a close [_] method.

Here is a reproducible patch that can be applied over https://github.com/clojure/tools.analyzer.jvm/commit/f00d92317307c3e9e326fd99d337292925dc9db1 :

https://gist.githubusercontent.com/vemv/ae450c380ac96683bc06275323e7e322/raw/91ad4b60502b32f4f57bd0d5707bcf51740f8e7b/gistfile1.patch