Re: [ClojureScript] Re: ClojureScript & Clojure 1.6.0

2014-07-06 Thread Yehonathan Sharvit
David, This compiltaion issue is still not solved. It prevents from me to upgrade to the latest clojurescript “0.0-2268” What is the proper channel to report this issue? On Tue, Jun 10, 2014 at 8:40 AM, David Nolen wrote: > Looks like new warnings from the Closure Compiler - something for > co

Re: [ClojureScript] Re: ClojureScript & Clojure 1.6.0

2014-06-09 Thread David Nolen
Looks like new warnings from the Closure Compiler - something for core.async to address. Thanks for the report! David On Tue, Jun 10, 2014 at 12:55 AM, Yehonathan Sharvit wrote: > > > I have compilation warnings related to core.async. Here is the log: > > Compiling "resources/public/js/main.js"

Re: ClojureScript & Clojure 1.6.0

2014-06-09 Thread Yehonathan Sharvit
I have compilation warnings related to core.async. Here is the log: Compiling "resources/public/js/main.js" from ["src/cljs"]... Jun 10, 2014 7:49:49 AM com.google.javascript.jscomp.LoggerErrorManager println WARNING: /Users/viebel/libs/klozzer/target/cljsbuild-compiler-0/cljs/core/async.js:127

Re: ClojureScript & Clojure 1.6.0

2014-06-09 Thread David Nolen
That's great to hear, the feedback is much appreciated. David On Mon, Jun 9, 2014 at 1:06 PM, Karsten Schmidt wrote: > Hi David, this is great! I've switched to this branch, updated all hashing > impls of deftypes in my library and it works without a hitch and see much > less hash collisions in

Re: ClojureScript & Clojure 1.6.0

2014-06-09 Thread Karsten Schmidt
Hi David, this is great! I've switched to this branch, updated all hashing impls of deftypes in my library and it works without a hitch and see much less hash collisions in large 3d meshes as a result. Awesome! K. On 8 Jun 2014 18:07, "David Nolen" wrote: > 1.6.0 branch is ready to be tested > h

Re: ClojureScript & Clojure 1.6.0

2014-06-08 Thread David Nolen
1.6.0 branch is ready to be tested http://github.com/clojure/clojurescript/tree/1.6.0, please give it a try in your projects. You can install this version of ClojureScript by * checking out the repo * git checkout 1.6.0 * ./script/install Take note of the version number that gets installed into y

Re: ClojureScript & Clojure 1.6.0

2014-06-08 Thread David Nolen
I don't think we want cut such a release just yet. I think it would be more informative to understand what's holding people off of 1.6.0. David On Sat, Jun 7, 2014 at 4:42 PM, Joshua Ballanco wrote: > At the risk of suggesting something completely heretical… > > Would it be possible to declare

Re: ClojureScript & Clojure 1.6.0

2014-06-06 Thread David Nolen
Given the feedback so far such a request seems to be in the minority. You could run a separate project for the CLJS parts. That said, is there something in the latest release (0.0-2227) that you find problematic that you can't continue with it? David On Fri, Jun 6, 2014 at 8:36 PM, Matching Socks

Re: ClojureScript & Clojure 1.6.0

2014-06-06 Thread Matching Socks
Can a lein-cljsbuild clj+cljs project specify separate versions of Clojure for the cljs and clj parts? If not, please give it another 6 months. On Friday, June 6, 2014 10:43:42 AM UTC-4, David Nolen wrote: > > Future releases of ClojureScript will have a hard dependency on Clojure > 1.6.0

Re: [ClojureScript] Re: ClojureScript & Clojure 1.6.0

2014-06-06 Thread Mimmo Cosenza
that’s great. thanks Nicola mimmo On 06 Jun 2014, at 19:48, Nicola Mometto wrote: > > For that matters, I'm working on writing tools.analyzer.js and the > minimum clojure version supported will be 1.4.0 > > Nicola > > > Chris Granger writes: > >> Since I doubt there'd be any others, I'll be

Re: [ClojureScript] Re: ClojureScript & Clojure 1.6.0

2014-06-06 Thread Nicola Mometto
For that matters, I'm working on writing tools.analyzer.js and the minimum clojure version supported will be 1.4.0 Nicola Chris Granger writes: > Since I doubt there'd be any others, I'll be the only dissenter ;) > > People already get mad Light Table requiring 1.5 since we use CLJS to do > an

Re: [ClojureScript] Re: ClojureScript & Clojure 1.6.0

2014-06-06 Thread David Nolen
My hope is that the GSoC analyzer work will allow ClojureScript and projects like LT to share an analyzer without the hassle of conflicting release cycles. Any help to expedite this decoupling is of course appreciated. David On Fri, Jun 6, 2014 at 1:43 PM, Chris Granger wrote: > Since I doubt

Re: [ClojureScript] Re: ClojureScript & Clojure 1.6.0

2014-06-06 Thread Chris Granger
Since I doubt there'd be any others, I'll be the only dissenter ;) People already get mad Light Table requiring 1.5 since we use CLJS to do analysis and such. Bumping it up to 1.6 means it'd be a long time before we could move our version of CLJS again. Maybe that's not a real issue and really jus

Re: ClojureScript & Clojure 1.6.0

2014-06-06 Thread Mimmo Cosenza
+1 mimmo On 06 Jun 2014, at 19:22, Andrey Antukh wrote: > +1 > > > 2014-06-06 19:19 GMT+02:00 Karsten Schmidt : > +1 > > On 6 Jun 2014 16:59, "David Nolen" wrote: > Clojure 1.6.0 introduced Murmur3 for much improved collection hashing and > several new functions & macros. There's very littl

Re: ClojureScript & Clojure 1.6.0

2014-06-06 Thread Andrey Antukh
+1 2014-06-06 19:19 GMT+02:00 Karsten Schmidt : > +1 > On 6 Jun 2014 16:59, "David Nolen" wrote: > >> Clojure 1.6.0 introduced Murmur3 for much improved collection hashing and >> several new functions & macros. There's very little incentive to continue >> to support 1.5.X given these enhancemen

Re: ClojureScript & Clojure 1.6.0

2014-06-06 Thread Karsten Schmidt
+1 On 6 Jun 2014 16:59, "David Nolen" wrote: > Clojure 1.6.0 introduced Murmur3 for much improved collection hashing and > several new functions & macros. There's very little incentive to continue > to support 1.5.X given these enhancements. > > David > > > On Fri, Jun 6, 2014 at 11:48 AM, Joshua

Re: ClojureScript & Clojure 1.6.0

2014-06-06 Thread David Nolen
Clojure 1.6.0 introduced Murmur3 for much improved collection hashing and several new functions & macros. There's very little incentive to continue to support 1.5.X given these enhancements. David On Fri, Jun 6, 2014 at 11:48 AM, Joshua Ballanco wrote: > No objection, but I’m curious what are