Re: [ANN] Clojure 1.9.0-RC1

2017-11-24 Thread Sergey Didenko
Code with reflection is ~6% faster on server JRE (in 1.9.0-RC1) and ~1% slower on client JRE. So apparently it's not a big deal. Server JRE: user> *clojure-version* {:major 1, :minor 8, :incremental 0, :qualifier nil} user> (use 'criterium.core) nil user> (bench (.length (.toString (reduce (fn [s

Re: [ANN] Clojure 1.9.0-RC1

2017-11-23 Thread Sergey Didenko
Correction - it's not about regex parsing. I removed reflection calls for StringBuilder and now it seems to be on par in speed. On Fri, Nov 24, 2017 at 1:20 AM, Sergey Didenko wrote: > Hi, > > is it expected that code which does a lot of regex parsing is ~14% slower > than it was under Clojure 1

Re: [ANN] Clojure 1.9.0-RC1

2017-11-23 Thread Sergey Didenko
Hi, is it expected that code which does a lot of regex parsing is ~14% slower than it was under Clojure 1.8? On Tue, Nov 14, 2017 at 8:22 AM, Shantanu Kumar wrote: > Sorry, my bad. I can see the same behavior in previous Clojure versions > too. I discovered this in the middle of moving to 1.9.0

Re: [ANN] Clojure 1.9.0-RC1

2017-11-13 Thread Shantanu Kumar
Sorry, my bad. I can see the same behavior in previous Clojure versions too. I discovered this in the middle of moving to 1.9.0-RC1 in one of the projects and somehow got it all mixed up. Shantanu On Tuesday, 14 November 2017 11:36:30 UTC+5:30, Andy Fingerhut wrote: > > I see the same behavior

Re: [ANN] Clojure 1.9.0-RC1

2017-11-13 Thread Andy Fingerhut
I see the same behavior in Clojure 1.7.0 and 1.8.0 as you see in 1.9.0-RC1. Andy On Mon, Nov 13, 2017 at 9:48 PM, Shantanu Kumar wrote: > Sorry, I did not specify the problem completely earlier. The coercion > fails only when *uncheked-math* is set to truthy in 1.9.0-RC1. > > user=> (byte \a) >

Re: [ANN] Clojure 1.9.0-RC1

2017-11-13 Thread Shantanu Kumar
Sorry, I did not specify the problem completely earlier. The coercion fails only when *uncheked-math* is set to truthy in 1.9.0-RC1. user=> (byte \a) 97 user=> (set! *unchecked-math* true) ; or :warn-on-boxed true user=> (byte \a) ClassCastException java.lang.Character cannot be cast to java.la

Re: [ANN] Clojure 1.9.0-RC1

2017-11-13 Thread Alex Miller
Works for me in 1.9.0-RC1. I don't know of anything that changed in this area. Clojure 1.9.0-RC1 user=> (byte \a) 97 On Mon, Nov 13, 2017 at 1:09 PM, Shantanu Kumar wrote: > The coercion (byte \a) works fine in Clojure 1.8, but it fails with > `ClassCastException java.lang.Character cannot be c

Re: [ANN] Clojure 1.9.0-RC1

2017-11-13 Thread Shantanu Kumar
The coercion (byte \a) works fine in Clojure 1.8, but it fails with `ClassCastException java.lang.Character cannot be cast to java.lang.Number` in 1.9.0-RC1. Is this by design? Shantanu On Monday, 13 November 2017 07:32:00 UTC+5:30, Alex Miller wrote: > > Hi David, > > Clojure 1.9 now depends

Re: [ANN] Clojure 1.9.0-RC1

2017-11-12 Thread Alex Miller
Hi David, Clojure 1.9 now depends on two external dependencies (spec.alpha and core.specs.alpha) so the instructions listed there will no longer work. We are evaluating whether and how to update those instructions in the readme right now. Most Clojure users work with Clojure through a project

Re: [ANN] Clojure 1.9.0-RC1

2017-11-12 Thread David Kinzer
I'm getting an error when I follow the instructions in the readme.txt, am I missing something? java -cp clojure-1.9.0-RC1.jar clojure.main Exception in thread "main" java.lang.ExceptionInInitializerError at java.base/java.lang.Class.forName0(Native Method) at java.base/java.lang.C

Re: [ANN] Clojure 1.9.0-RC1

2017-11-10 Thread Alex Miller
Clojure 1.9 (and 1.8, and every other prior version of Clojure!) works with Java 9 due to the care that Java takes in retaining backward compatibility. Clojure 1.0 works just fine with Java 9. However, there have been some changes that affect various tools, most prominently Leiningen and Boot.

Re: [ANN] Clojure 1.9.0-RC1

2017-11-10 Thread Didier
Is Clojure 1.9 expected to support JDK9? Or is that support reserved for a later version? On Friday, 10 November 2017 10:08:35 UTC-8, Beau Fabry wrote: > > We've switched both of our main projects to RC1 and have had no issues yet. > > On Thursday, November 9, 2017 at 11:49:07 PM UTC-8, Sean Corf

Re: [ANN] Clojure 1.9.0-RC1

2017-11-10 Thread Beau Fabry
We've switched both of our main projects to RC1 and have had no issues yet. On Thursday, November 9, 2017 at 11:49:07 PM UTC-8, Sean Corfield wrote: > > We have three processes running RC1 in production as of today. Looks good > so far. We’ve had everything else up and running on Beta 4 in produc

RE: [ANN] Clojure 1.9.0-RC1

2017-11-09 Thread Sean Corfield
We have three processes running RC1 in production as of today. Looks good so far. We’ve had everything else up and running on Beta 4 in production since Monday, also looking good. Sean Corfield -- (970) FOR-SEAN -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "If you're not annoyi

Re: [ANN] Clojure 1.9.0-RC1

2017-11-09 Thread Alex Miller
Thanks, that’s good to hear. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from th

Re: [ANN] Clojure 1.9.0-RC1

2017-11-09 Thread Rick Moynihan
One more data point. I haven't uncovered any regressions yet on beta4 & have upgraded a few libraries and apps; though none are in production yet I've been working with it more or less daily since the beta4 release. R. On 7 November 2017 at 14:58, Alex Miller wrote: > Clojure 1.9.0-RC1 is now