Please be aware that we expect to make changes to the API package and class 
name in the next alpha based on a discussion today so you may want to wait for 
RC for that!



On Nov 22, 2013, at 11:06 PM, <seancorfi...@gmail.com> wrote:

> Thank you.
> 
> I’d like to take this opportunity to thank the Clojure/core team for the 
> slow, measured pace of development and stability of Clojure. 1.6 looks like a 
> safe, gentle upgrade from 1.5.1.
> 
> Ironically the biggest change for me in 1.6 is the new API stuff - I look 
> forward to rewriting my cfmljure library to leverage the new API once it goes 
> gold! 😊
> 
> Sean Corfield -- (904) 302-SEAN
> An Architect's View -- http://corfield.org
> 
> From: Alex Miller
> Sent: ‎Friday‎, ‎November‎ ‎22‎, ‎2013 ‎7‎:‎26‎ ‎PM
> To: clojure@googlegroups.com
> 
> Clojure 1.6.0-alpha3 is now available. 
>  
> Try it via 
> - Download: http://central.maven.org/maven2/org/clojure/clojure/1.6.0-alpha3/
> - Leiningen: [org.clojure/clojure "1.6.0-alpha3"]
> 
> Clojure 1.6.0-alpha3 has the following changes from 1.6.0-alpha2:
> 
> 1) Reverted: CLJ-1125 (fix for permgen leak) based on the regression reported 
> in CLJ-1299. A fix for this regression is in development and I expect it to 
> be re-applied in a future alpha.
> - http://dev.clojure.org/jira/browse/CLJ-1125
> - http://dev.clojure.org/jira/browse/CLJ-1299
> 
> 2) The following features are no longer marked "Alpha" in Clojure (woohoo!):
> 
> * Watches - add-watch, remove-watch
> * Transients - transient, persistent!, conj!, assoc!, dissoc!, pop!, disj!
> * Exception data - ex-info, ex-data
> * Promises - promise, deliver
> * Records - defrecord
> * Types - deftype
> * Pretty-print tables - print-table
> 
> 3) Applied patches for:
> 
> * [CLJ-827](http://dev.clojure.org/jira/browse/CLJ-827) - New function: 
> clojure.core/unsigned-bit-shift-right
> * [CLJ-866](http://dev.clojure.org/jira/browse/CLJ-866) - New function: 
> clojure.test/test-vars
> * [CLJ-1102](http://dev.clojure.org/jira/browse/CLJ-1102) - Better handling 
> of exceptions with empty stack traces.
> * [CLJ-939](http://dev.clojure.org/jira/browse/CLJ-939) - Exceptions thrown 
> in the top level ns form are reported without file or line number.
> * [CLJ-858](http://dev.clojure.org/jira/browse/CLJ-858) - Improve speed of 
> STM by removing System.currentTimeMillis.
> * [CLJ-669](http://dev.clojure.org/jira/browse/CLJ-669) - 
> clojure.java.io/do-copy: use java.nio for Files
> * [CLJ-1105](http://dev.clojure.org/jira/browse/CLJ-1105) - clojure.walk now 
> supports records.
> * [CLJ-949](http://dev.clojure.org/jira/browse/CLJ-949) - Removed all 
> unnecessary cases of sneakyThrow.
> * [CLJ-1238](http://dev.clojure.org/jira/browse/CLJ-1238) - Allow EdnReader 
> to read foo// (matches LispReader behavior).
> * [CLJ-1264](http://dev.clojure.org/jira/browse/CLJ-1264) - Remove uses of _ 
> as a var in the Java code (causes warning in Java 8).
> * [CLJ-1222](http://dev.clojure.org/jira/browse/CLJ-1222) - Multiplication 
> overflow issues around Long/MIN_VALUE
> * [CLJ-1118](http://dev.clojure.org/jira/browse/CLJ-1118) - Inconsistent 
> numeric comparison semantics between BigDecimals and other numerics
> 
> 3) Full change log is updated as well:
> https://github.com/clojure/clojure/blob/master/changes.md
> 
> Still on the plate are 16 tickets (I expect many but not all of those to make 
> it in) and the hashing performance work 
> (http://dev.clojure.org/display/design/Better+hashing). Once we reach 
> "completion" we'll release an RC for final testing.
> 
> Alex Miller
> 
> -- 
> -- 
> 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 this group, send email to
> clojure+unsubscr...@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+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
> -- 
> -- 
> 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 this group, send email to
> clojure+unsubscr...@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 a topic in the Google 
> Groups "Clojure" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/clojure/zM6cbhuBNxY/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

-- 
-- 
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 this group, send email to
clojure+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to