Re: [ClojureScript] Re: cljsbuild/closure compiler options

2014-12-24 Thread David Nolen
Thanks for pointing this out. Fixed in master thanks to your patch. Also landed a patch which should cover more problematic warning cases around arithmetic. David On Wed, Dec 24, 2014 at 8:04 AM, Thomas Heller wrote: > Hey, > > I just looked at the warnings code and it seems like a mistake that

[ClojureScript] Re: cljsbuild/closure compiler options

2014-12-24 Thread tcr1272
I see, and thanks for the solution with pointers Thomas. Cheers, Tim -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group a

[ClojureScript] Re: cljsbuild/closure compiler options

2014-12-24 Thread Thomas Heller
Hey, I just looked at the warnings code and it seems like a mistake that disabling one warning actually disables 3 by accident. Anyways, the warning definitions [1] are all pretty self explanatory, more so if you look at the actual text the produce in the error functions below [1]. You could

[ClojureScript] Re: cljsbuild/closure compiler options

2014-12-24 Thread tcr1272
> Did you run `lein clean && lein cljsbuild clean` after the upgrade? Yes. The arithmetic error occurs whenever I have an input arg that is bound. I believe the compiler sees this as a var and not a number and therefore yaks a warning. That said I'm not sure why my last version from 3 months

[ClojureScript] Re: cljsbuild/closure compiler options

2014-12-23 Thread Jonas Enlund
Did you run `lein clean && lein cljsbuild clean` after the upgrade? On Wednesday, December 24, 2014 8:12:30 AM UTC+2, tcr...@gmail.com wrote: > A recent upgrade has introduced a bunch of new warnings of these types: > > 1. cljs.core/+, all arguments must be numbers, got [#{nil clj-nil} #{nil any