You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm seeing an "Arities must be distinct" RuntimeException when running lein uberjar with direct linking (-Dclojure.compiler.direct-linking=true) enabled.
Caused by: java.lang.RuntimeException: Arities must be distinct
at schema.core$make_fn_schema.invokeStatic(core.clj:1049)
at metabase.driver.query_processor.expand$fn__20187.invokeStatic(expand.clj:101)
...
It's being triggered by a 2-arity s/defn function that looks like this:
The text was updated successfully, but these errors were encountered:
camsaul
changed the title
"Arities must be distinct" error when compiling jar in Clojure 1.8
"Arities must be distinct" error when using direct linking in Clojure 1.8
Feb 13, 2016
Thanks for the report. I don't see why it shouldn't work. I have no experience with direct linking and can't reproduce with this example, so if you could provide a test project that exhibits the error (or dig in further yourself) that would be a big help. Thanks again!
I looked into it and the issue seems to be that there are two copies of the
schema.core.One class floating around in this AOT compilation setting.
This causes the (instance? One ...) check in arity- to return false on
both arities (when it should return true on both), which causes the
assertion failure.
I've never used AOT myself so I'm not sure where to go from here, however.
I'm seeing an "Arities must be distinct"
RuntimeException
when runninglein uberjar
with direct linking (-Dclojure.compiler.direct-linking=true
) enabled.It's being triggered by a 2-arity
s/defn
function that looks like this:The text was updated successfully, but these errors were encountered: