[ANN] Clojure 1.3 Beta 2

122 views
Skip to first unread message

Christopher Redinger

unread,
Aug 29, 2011, 10:28:57 AM8/29/11
to clo...@googlegroups.com
Clojure 1.3 Beta 2 is now available at 


The list of changes:

  * clojure.test/*/*-report vars made dynamic for use with external
    tools.
  * Calls favor arg vectors :tag over var :tag (CLJ-811)
  * BigInt ops made faster when values are small enough to be treated as longs
  * rational? metadata fixed
  * partition and partition-all holds less
  * Bug fixed on transient vectors
  * print-dup and print-method removed for deftypes (CLJ-812)
  * Prevent make-parents NPE, (CLJ-808)
  * Special print support removed for BigIntegers. (CLJ-798)

Please grab it and let us know how it works for you.

Thanks!

--
Chris Redinger
Clojure/core

Armando Blancas

unread,
Aug 30, 2011, 12:06:09 AM8/30/11
to Clojure
The change to beta2 isn't working for me:

<dependency>
<groupId>org.clojure</groupId>
<artifactId>clojure</artifactId>
<version>1.3.0-beta2</version>
</dependency>

1.3.0-beta1 works fine.

Armando Blancas

unread,
Aug 30, 2011, 12:34:18 AM8/30/11
to Clojure
False alarm. Some trouble with the VPN line.

Isaac Gouy

unread,
Aug 30, 2011, 1:52:38 AM8/30/11
to Clojure
Not surprisingly, some of the benchmarks game programs written for
Clojure 1.2 have problems with 1.3 Beta 2.

My guess is that small changes to the programs will be required to
catch up with the new version, but occasionally program failures have
indicated a bug in new versions of other languages.

Mon 15:17:15 ...OK .....binarytrees.clojure-5.clojure [33]
Mon 15:21:02 ...OK .....binarytrees.clojure-4.clojure [32]
Mon 15:30:04 ...OK .....binarytrees.clojure [31]
Mon 15:37:59 ...OK .....binarytrees.clojure-2.clojure [30]
Mon 15:49:27 ...OK .....binarytrees.clojure-3.clojure [29]
Mon 15:54:51 ...OK fannkuchredux.clojure-2.clojure [28]
Mon 15:58:54 ...OK .....fasta.clojure-2.clojure [27]
Mon 16:00:21 ...OK .....fasta.clojure [26]
Mon 16:02:01 .PROGRAM FAILED fasta.clojure-4.clojure [25]
Mon 16:02:04 .PROGRAM FAILED fasta.clojure-3.clojure [24]
Mon 16:02:07 .PROGRAM FAILED fastaredux.clojure-4.clojure [23]
Mon 16:02:10 .PROGRAM FAILED knucleotide.clojure-3.clojure [22]
Mon 16:02:12 ...OK knucleotide.clojure-2.clojure [21]
Mon 16:10:07 ...OK knucleotide.clojure [20]
Mon 16:21:06 ...OK .....mandelbrot.clojure [19]
Mon 16:29:08 .PROGRAM FAILED mandelbrot.clojure-3.clojure [18]
Mon 16:29:11 .PROGRAM FAILED mandelbrot.clojure-4.clojure [17]
Mon 16:29:14 ...OK .....mandelbrot.clojure-2.clojure [16]
Mon 16:37:06 .PROGRAM FAILED meteor.clojure [15]
Mon 16:37:12 ...TIMED OUT nbody.clojure-2.clojure [14]
Mon 17:47:43 .PROGRAM FAILED pidigits.clojure [13]
Mon 17:47:46 ...OK .....regexdna.clojure-3.clojure [12]
Mon 17:52:45 .PROGRAM FAILED regexdna.clojure-2.clojure [11]
Mon 17:52:47 ...PROGRAM FAILED .....revcomp.clojure [10]
Mon 17:53:38 ...PROGRAM FAILED .....revcomp.clojure-2.clojure [9]
Mon 18:03:45 ...OK .....revcomp.clojure-4.clojure [8]
Mon 18:04:31 ...OK .....revcomp.clojure-3.clojure [7]
Mon 18:05:07 ...OK .....spectralnorm.clojure-5.clojure [6]
Mon 18:09:07 ...OK .....spectralnorm.clojure-7.clojure [5]
Mon 18:11:06 ...OK .....spectralnorm.clojure-2.clojure [4]
Mon 18:16:31 ...OK .....spectralnorm.clojure-6.clojure [3]
Mon 18:18:28 ...TIMED OUT .....threadring.clojure [2]
Mon 19:21:30 ...TIMED OUT .....threadring.clojure-2.clojure [1]

(Note reverse-complement and reverse-complement #2 fail because
memory settings were requested to show reduced Clojure memory usage on
the other reverse-complement programs.)

The program source code, with build and run logs can be reached from
the program name links -

http://shootout.alioth.debian.org/u64/measurements.php?lang=clojure

Andy Fingerhut

unread,
Sep 1, 2011, 1:07:31 AM9/1/11
to clo...@googlegroups.com
Isaac, all of the programs that fail with Clojure 1.3 now can be made to compile and run on both 1.2 and 1.3 by changing a relatively small part of the programs.

I have them on my computer (and probably checked into the github repo clojure-benchmarks), but haven't put them on the benchmarks game web site because it adds a bit of unnecessary clutter to programs that were only intended to run on Clojure 1.2 when they were written.

Does the fact that you produced these test results mean that you are considering moving to Clojure 1.3 soon on the benchmarks game web site?

If so, I can contribute the small modifications necessary.  Rich Hickey has written a quite different Clojure 1.3-specific program for the binarytrees benchmark that is noticeably faster than the Clojure 1.2 program, but there is no reason to submit that until the site uses Clojure 1.3.

Andy


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

Isaac Gouy

unread,
Sep 1, 2011, 8:50:33 AM9/1/11
to Clojure


On Aug 31, 10:07 pm, Andy Fingerhut <andy.finger...@gmail.com> wrote:
> Isaac, all of the programs that fail with Clojure 1.3 now can be made to
> compile and run on both 1.2 and 1.3 by changing a relatively small part of
> the programs.
>
> I have them on my computer (and probably checked into the github repo
> clojure-benchmarks), but haven't put them on the benchmarks game web site
> because it adds a bit of unnecessary clutter to programs that were only
> intended to run on Clojure 1.2 when they were written.
>
> Does the fact that you produced these test results mean that you are
> considering moving to Clojure 1.3 soon on the benchmarks game web site?


When Clojure 1.3 is released - and obviously the beta already is being
shown on those /u64 pages.


> If so, I can contribute the small modifications necessary.  

Cool - send 'em in!


> Rich Hickey has written a quite different Clojure 1.3-specific program...

Well as the author, he'd have to contribute that.

Reply all
Reply to author
Forward
0 new messages