Skip to content
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

Analyser fails with "Invalid symbol" error (Clojure 1.12 interop symbol) #410

Open
scramjet opened this issue Mar 17, 2025 · 6 comments · May be fixed by #411
Open

Analyser fails with "Invalid symbol" error (Clojure 1.12 interop symbol) #410

scramjet opened this issue Mar 17, 2025 · 6 comments · May be fixed by #411

Comments

@scramjet
Copy link

scramjet commented Mar 17, 2025

Fails with:

java.util.concurrent.ExecutionException: clojure.lang.ExceptionInfo: [line 30, col 33] Invalid symbol: long/1. {:type :reader-exception, :ex-kind :reader-error, :file "/Users/matt/Development/systematic-basis/src/systematic/doorkeeper/views/common/issue_stats.clj", :line 30, :col 33}

Code:

(defn count-extra-stats [^long/1 custom-counts custom-query-config issue query-context]
  (loop [index 0]
    ...)))

Environment

[org.clojure/clojure "1.12.0"]
[nrepl/nrepl "1.3.1"]
[cider/cider-nrepl "0.52.1"]
[refactor-nrepl/refactor-nrepl "3.10.0"]
@vemv
Copy link
Member

vemv commented Mar 17, 2025

Thanks for the report!

It might be a matter of upgrading tools.analyzer if they got support for that syntax already.

@scramjet
Copy link
Author

Was hoping that would be the case, but tools.analyzer hasn't been updated since Clojure 1.12 was released in September 2024, so I'd guess not.

@vemv
Copy link
Member

vemv commented Mar 17, 2025

@scramjet
Copy link
Author

You're right, I was looking at the wrong repo (tools.analyzer, not tools.analyzer.jvm), sorry.

@vemv vemv linked a pull request Mar 18, 2025 that will close this issue
@vemv
Copy link
Member

vemv commented Mar 18, 2025

I got it almost there #411 but there's a stubborn test

These days I don't have time for OSS and already allocated a bit this morning. If you (or someone else) get to fix it, we'll release it, else it will have to wait

Cheers - V

@scramjet
Copy link
Author

Thanks for that, much appreciated.

I don't have time to get into this now unfortunately, but perhaps @bbatsov's suggestion to ignore the test for now will end up being acceptable.

Cheers,

Matt.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants