Re: Compilation failure to reject arguments matching formal parameters

2014-08-15 Thread Andy Fingerhut
I don't know how hard or easy it might be to implement a check like this in a lint tool like Eastwood, but I've created a Github issue for it with the idea, linking to this discussion, in case someone thinks of a way. https://github.com/jonase/eastwood/issues/83 Andy On Fri, Aug 15, 2014 at

Re: Compilation failure to reject arguments matching formal parameters

2014-08-15 Thread Reid McKenzie
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Comments inline On 08/15/2014 06:47 AM, Dave Tenny wrote: > This is getting old. Any suggestions or plans to fix it? Do I need to use > some other common declaration style for functions? > > ; CIDER 0.5.0 (Clojure 1.6.0, nREPL 0.2.3) > user> (defn

Re: Compilation failure to reject arguments matching formal parameters

2014-08-15 Thread Jonah Benton
Hi Dave, Somewhat related: I've been looking at Prismatic's Schema [1] along with ordinary pre and post conditions to apply stricter runtime controls on suites of functions that take and return maps: user=> (require '[schema.core :as sc]) nil user=> (def FooIn "FooIn must have a string at :bar,

Compilation failure to reject arguments matching formal parameters

2014-08-15 Thread Dave Tenny
This is getting old. Any suggestions or plans to fix it? Do I need to use some other common declaration style for functions? ; CIDER 0.5.0 (Clojure 1.6.0, nREPL 0.2.3) user> (defn foo [& {:keys [bar]}] bar) #'user/foo user> (foo :baz 1) nil In my opinion the compilation of the call to foo sho