Thanx for the specific example! Yeah, I've used :arglists for "examples" in a couple of places instead of actual argument lists. I'll fix that in 0.3.3 and may do the same with CongoMongo (although it's a far worse culprit in several areas - and we're in the process of migrating to Monger now anyway).
Sean On Jan 13, 2014, at 11:49 AM, Nicola Mometto <brobro...@gmail.com> wrote: > Sean, it looks like the issue is caused by arglists like this one: > https://github.com/clojure/java.jdbc/blob/master/src/main/clojure/clojure/java/jdbc.clj#L782-L783 > > tools.analyzer.jvm uses :arglists to detect possible invoke calls with a > misplaced arity, expecting that to be a valid value, in your case for > documentation purposes you are attaching a :arglists that does not match > a valid list of args vector, so t.a.j interprets that as a 6-arity > arglist. > > Nicola > > > Sean Corfield (Clojure) writes: > >> Just started using this and I see the argslist caveat that causes >> Eastwood to misdiagnose :wrong-arity (the readme specifies java.jdbc >> 0.3.x but it also gets tripped up by congomongo). >> >> Can you (Andy or Jonas or any other Eastwood user) clarify how the >> arglists cause the problem and what, if anything, can be done in the >> source of java.jdbc and/or congomongo to alleviate the problem? >> >> Thanx, >> Sean
signature.asc
Description: Message signed with OpenPGP using GPGMail
