ClojureScript & Clojure 1.6.0

[David Nolen]

Future releases of ClojureScript will have a hard dependency on Clojure 1.6.0. If you have any objections, speak up now :)

David

[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 <jbal...@circleci.com> wrote:

No objection, but I’m curious what are the motivating factors? Are there any new features/bug-fixes planned for ClojureScript that will depend on Clojure 1.6.0 features? or is this just a case of keeping things as up-to-date as possible?

On Friday, June 6, 2014 at 17:43, David Nolen wrote:

> Future releases of ClojureScript will have a hard dependency on Clojure 1.6.0. If you have any objections, speak up now :)
>
> David
>

> --
> You received this message because you are subscribed to the Google Groups "Clojure Dev" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to clojure-dev...@googlegroups.com (mailto:clojure-dev...@googlegroups.com).
> To post to this group, send email to cloju...@googlegroups.com (mailto:cloju...@googlegroups.com).

> Visit this group at http://groups.google.com/group/clojure-dev.
> For more options, visit https://groups.google.com/d/optout.



--
You received this message because you are subscribed to the Google Groups "Clojure Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to clojure-dev...@googlegroups.com.
To post to this group, send email to cloju...@googlegroups.com.
Visit this group at http://groups.google.com/group/clojure-dev.
For more options, visit https://groups.google.com/d/optout.

[Karsten Schmidt]

+1

[Mimmo Cosenza]

+1

mimmo

On 06 Jun 2014, at 19:22, Andrey Antukh <ni...@niwi.be> wrote:

+1

+1

Groups "Clojure" group.
To post to this group, send email to clo...@googlegroups.com
Note that posts from new members are moderated - please be patient with your first post.
To unsubscribe from this group, send email to
clojure+u...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups "Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to clojure+u...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Andrey Antukh - Андрей Антух - <andrei....@kaleidos.net> / <ni...@niwi.be>

http://www.niwi.be

https://github.com/niwibe

--
You received this message because you are subscribed to the Google

Groups "Clojure" group.
To post to this group, send email to clo...@googlegroups.com
Note that posts from new members are moderated - please be patient with your first post.
To unsubscribe from this group, send email to
clojure+u...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups "Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to clojure+u...@googlegroups.com.

[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 just an indication that we shouldn't be using the CLJS analyzer for this stuff anymore, but figured I should mention.

Cheers,
Chris.

[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

[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

>> http://www.niwi.be <http://www.niwi.be/page/about/>

[Mimmo Cosenza]

that’s great.

thanks Nicola

mimmo

-- 

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 and stop receiving emails from it, send an email to clojurescrip...@googlegroups.com.
To post to this group, send email to clojur...@googlegroups.com.
Visit this group at http://groups.google.com/group/clojurescript.

[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 <phill...@gmail.com> wrote:

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. If you have any objections, speak up now :)

David

--

[Joshua Ballanco]

At the risk of suggesting something completely heretical…

Would it be possible to declare a v0.1 release before making the cut over to 1.6? At least then, if anyone were so inclined, those stuck on Clojure v1.5.1 for whatever reason could at least submit/backport critical bug-fixes for potential v0.1.1, etc. releases going forward.

On Saturday, June 7, 2014 at 4:16, David Nolen wrote:

> 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 <phill...@gmail.com (mailto:phill...@gmail.com)> wrote:
> >
> > 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. If you have any objections, speak up now :)
> > >
> > > David
> >
> > --
> > You received this message because you are subscribed to the Google
> > Groups "Clojure" group.

> > To post to this group, send email to clo...@googlegroups.com (mailto:clo...@googlegroups.com)

> > Note that posts from new members are moderated - please be patient with your first post.
> > To unsubscribe from this group, send email to

> > clojure+u...@googlegroups.com (mailto:clojure%2Bunsu...@googlegroups.com)

> > For more options, visit this group at
> > http://groups.google.com/group/clojure?hl=en
> > ---
> > You received this message because you are subscribed to the Google Groups "Clojure" group.

> > To unsubscribe from this group and stop receiving emails from it, send an email to clojure+u...@googlegroups.com (mailto:clojure+u...@googlegroups.com).

> > For more options, visit https://groups.google.com/d/optout.
>
>

> --
> You received this message because you are subscribed to the Google Groups "Clojure Dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to clojure-dev...@googlegroups.com (mailto:clojure-dev...@googlegroups.com).

> To post to this group, send email to cloju...@googlegroups.com (mailto:cloju...@googlegroups.com).
> Visit this group at http://groups.google.com/group/clojure-dev.

[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

To unsubscribe from this group and stop receiving emails from it, send an email to clojure-dev...@googlegroups.com.

To post to this group, send email to cloju...@googlegroups.com.

Visit this group at http://groups.google.com/group/clojure-dev.

[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 your local Maven. Use this in version number in your project.

David

[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.

[David Nolen]

That's great to hear, the feedback is much appreciated.

David

[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: WARNING - unreachable code
{return null;
^

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:178: WARNING - unreachable code
{return null;
^

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:420: WARNING - unreachable code
{return null;
^

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/impl/ioc_helpers.js:353: WARNING - unreachable code
{return null;
^

Jun 10, 2014 7:49:49 AM com.google.javascript.jscomp.LoggerErrorManager printSummary
WARNING: 0 error(s), 4 warning(s)

[David Nolen]

Looks like new warnings from the Closure Compiler - something for
core.async to address. Thanks for the report!

David

> --

> 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 and stop receiving emails from it, send an email to clojurescrip...@googlegroups.com.
> To post to this group, send email to clojur...@googlegroups.com.
> Visit this group at http://groups.google.com/group/clojurescript.

[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?

You received this message because you are subscribed to a topic in the Google Groups "ClojureScript" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/clojurescript/MEFJ5D7g8yM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to clojurescrip...@googlegroups.com.

To post to this group, send email to clojur...@googlegroups.com.
Visit this group at http://groups.google.com/group/clojurescript.

--

"Are we what we become or do we become what we are?" - Prof. Beno Gross

[David Nolen]

Those are just warnings they shouldn't prevent you from generating the
code. ClojureScript exposes Closure Compiler warning suppression. If
you find these particular warnings annoying you can toggle them:

:closure-warnings {:check-useless-code :off}

should do the trick in your build settings.

David

[Yehonathan Sharvit]

Thanks David

[Paul Butcher]

On 6 June 2014 at 15:43:32, David Nolen (dnolen...@gmail.com) wrote:

Future releases of ClojureScript will have a hard dependency on Clojure 1.6.0. If you have any objections, speak up now :)

No objection to the decision, but is there anything we can do to improve the error message if the wrong version of Clojure is used? This is what currently results if 0.0-2268 is used with Clojure 1.5.1:

clojure.lang.ExceptionInfo:  {:tag :cljs/analysis-error}

at clojure.core$ex_info.invoke(core.clj:4327)

at cljs.analyzer$error.invoke(analyzer.clj:268)

at cljs.analyzer$analyze.invoke(analyzer.clj:1522)

at cljs.analyzer$analyze.invoke(analyzer.clj:1519)

at cljs.compiler$parse_ns$fn__2635$fn__2636.invoke(compiler.clj:959)

at cljs.compiler$parse_ns$fn__2635.invoke(compiler.clj:959)

at cljs.compiler$parse_ns.invoke(compiler.clj:954)

at cljs.compiler$parse_ns.invoke(compiler.clj:949)

at cljs.compiler$to_target_file.invoke(compiler.clj:1037)

at cljs.compiler$compile_root.invoke(compiler.clj:1069)

at cljs.closure$compile_dir.invoke(closure.clj:341)

at cljs.closure$eval2976$fn__2977.invoke(closure.clj:381)

at cljs.closure$eval2913$fn__2914$G__2904__2921.invoke(closure.clj:292)

at cljs.closure$eval2963$fn__2964.invoke(closure.clj:395)

at cljs.closure$eval2913$fn__2914$G__2904__2921.invoke(closure.clj:292)

at cljsbuild.compiler.SourcePaths$fn__3172.invoke(compiler.clj:44)

at clojure.core$map$fn__4207.invoke(core.clj:2485)

at clojure.lang.LazySeq.sval(LazySeq.java:42)

at clojure.lang.LazySeq.seq(LazySeq.java:60)

at clojure.lang.RT.seq(RT.java:484)

at clojure.core$seq.invoke(core.clj:133)

at clojure.core$apply.invoke(core.clj:617)

at clojure.core$mapcat.doInvoke(core.clj:2514)

at clojure.lang.RestFn.invoke(RestFn.java:423)

at cljsbuild.compiler.SourcePaths._compile(compiler.clj:44)

at cljs.closure$build.invoke(closure.clj:955)

at cljs.closure$build.invoke(closure.clj:923)

at cljsbuild.compiler$compile_cljs$fn__3183.invoke(compiler.clj:58)

at cljsbuild.compiler$compile_cljs.invoke(compiler.clj:57)

at cljsbuild.compiler$run_compiler.invoke(compiler.clj:159)

at user$eval3309$iter__3327__3331$fn__3332$fn__3344.invoke(form-init5368135610584150646.clj:1)

at user$eval3309$iter__3327__3331$fn__3332.invoke(form-init5368135610584150646.clj:1)

at clojure.lang.LazySeq.sval(LazySeq.java:42)

at clojure.lang.LazySeq.seq(LazySeq.java:60)

at clojure.lang.RT.seq(RT.java:484)

at clojure.core$seq.invoke(core.clj:133)

at clojure.core$dorun.invoke(core.clj:2780)

at clojure.core$doall.invoke(core.clj:2796)

at user$eval3309.invoke(form-init5368135610584150646.clj:1)

at clojure.lang.Compiler.eval(Compiler.java:6619)

at clojure.lang.Compiler.eval(Compiler.java:6609)

at clojure.lang.Compiler.load(Compiler.java:7064)

at clojure.lang.Compiler.loadFile(Compiler.java:7020)

at clojure.main$load_script.invoke(main.clj:294)

at clojure.main$init_opt.invoke(main.clj:299)

at clojure.main$initialize.invoke(main.clj:327)

at clojure.main$null_opt.invoke(main.clj:362)

at clojure.main$main.doInvoke(main.clj:440)

at clojure.lang.RestFn.invoke(RestFn.java:421)

at clojure.lang.Var.invoke(Var.java:419)

at clojure.lang.AFn.applyToHelper(AFn.java:163)

at clojure.lang.Var.applyTo(Var.java:532)

at clojure.main.main(main.java:37)

Caused by: java.lang.NullPointerException

at cljs.core$import_macros$fn__3382.invoke(core.clj:49)

at clojure.core$map$fn__4207.invoke(core.clj:2485)

at clojure.lang.LazySeq.sval(LazySeq.java:42)

at clojure.lang.LazySeq.seq(LazySeq.java:60)

at clojure.lang.RT.seq(RT.java:484)

at clojure.core$seq.invoke(core.clj:133)

at clojure.core$map$fn__4211.invoke(core.clj:2490)

at clojure.lang.LazySeq.sval(LazySeq.java:42)

at clojure.lang.LazySeq.seq(LazySeq.java:67)

at clojure.lang.RT.seq(RT.java:484)

at clojure.core$seq.invoke(core.clj:133)

at clojure.core$concat$cat__3925$fn__3926.invoke(core.clj:687)

at clojure.lang.LazySeq.sval(LazySeq.java:42)

at clojure.lang.LazySeq.seq(LazySeq.java:60)

at clojure.lang.Cons.next(Cons.java:39)

at clojure.lang.RT.next(RT.java:598)

at clojure.lang.Compiler.eval(Compiler.java:6606)

at clojure.lang.Compiler.load(Compiler.java:7064)

at clojure.lang.RT.loadResourceScript(RT.java:370)

at clojure.lang.RT.loadResourceScript(RT.java:361)

at clojure.lang.RT.load(RT.java:440)

at clojure.lang.RT.load(RT.java:411)

at clojure.core$load$fn__5018.invoke(core.clj:5530)

at clojure.core$load.doInvoke(core.clj:5529)

at clojure.lang.RestFn.invoke(RestFn.java:408)

at cljs.analyzer$load_core.invoke(analyzer.clj:210)

at cljs.analyzer$analyze$fn__1650.invoke(analyzer.clj:1528)

at cljs.analyzer$analyze.invoke(analyzer.clj:1524)

... 50 more

--
paul.butcher->msgCount++

Silverstone, Brands Hatch, Donington Park...
Who says I have a one track mind?

http://www.paulbutcher.com/
LinkedIn: http://www.linkedin.com/in/paulbutcher
Skype: paulrabutcher

Author of Seven Concurrency Models in Seven Weeks: When Threads Unravel

http://pragprog.com/book/pb7con