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
Right now t.a(.j) libs always use :arglists of a function to check whether there is a call with incorrect arity.
In very recent work on Eastwood I have added a filter that suppresses such warnings if the call has an allowed number of args according to a different set of arglists in Eastwood's configuration.
That is good for suppressing wrong warnings, but it is bad in that it will never catch some calls with wrong arities, because they have allowed arities according to the :arglists contents. It would be best if t.a(.j) used the same arglists that Eastwood does elsewhere.
The text was updated successfully, but these errors were encountered:
Perhaps more appropriate would be for Eastwood to ignore the :maybe-arity-mismatch key in the ASTs produced by t.a(.j), and implement its own independent check for all :op :invoke ASTs.
jafingerhut
changed the title
Make t.a(.j) libs use Eastwood-supplied arglists for :maybe-arity-mismatch tagging
Improve wrong-arity linter slightly
Dec 12, 2014
Right now t.a(.j) libs always use :arglists of a function to check whether there is a call with incorrect arity.
In very recent work on Eastwood I have added a filter that suppresses such warnings if the call has an allowed number of args according to a different set of arglists in Eastwood's configuration.
That is good for suppressing wrong warnings, but it is bad in that it will never catch some calls with wrong arities, because they have allowed arities according to the :arglists contents. It would be best if t.a(.j) used the same arglists that Eastwood does elsewhere.
The text was updated successfully, but these errors were encountered: