10 ms·
Clojure 1.2 Beta
- rje 16y agoList of changes in 1.2: http://github.com/clojure/clojure/blob/1.2.x/changes.txt http://github.com/clojure/clojure/blob/1.2.x/changes.txt
- bitsai 16y agoI'm extremely excited about "case". It's the one thing I missed the most from Haskell & Scala.
- praptak 16y agoC'mon, (condp = ...) was not that bad :)
- jcromartie 16y agocondp was rough for me. It requires too much shifting around of the pieces to figure out what it was doing.
- praptak 16y agoI don't believe there is very much gain in code clarity here. The core benefit of case over condp is efficiency. The condp is linear (goes over each clause until one matches) and case builds a very efficient dispatch function during compile time. This is why case only takes compile-time constant expressions.
- gtani 16y agoSame day as scala 2.8.0 final http://www.scala-lang.org/node/7009 http://www.scala-lang.org/node/7009
- francoisdevlin 16y agoYeah, except Clojure is more awesome :-p
- gtani 16y agoSorry about that, I'm not usually a thread hijacker. Q: is the plan to have point releases (1.2.1) to roll up e.g. stuff from prim, num, equal branches?
- francoisdevlin 16y agoClojure has never really had a point release before, so who knows.
- swannodette 16y agoI'm pretty sure that's something planned for 1.3
- mark_l_watson 16y agoThat is cool also! For a long time I was experimenting a lot with both Clojure and Scala, but then I took a gig with a Clojure shop earlier this year. Scala is still on my short list of languages I would use for my own projects (as is Racket Scheme, BTW).
- Calamitous 16y agoJust curious, as you seem to imply that Clojure is no longer on that list. If this is the case, why not?
- mark_l_watson 16y agoNo, I like Clojure - but as a platform, it needs some time to get everything right. I think some patience is required, let the Clojure platform developers keep up their very good work.
- 16y ago
- mark_l_watson 16y agoAren't just about everyone already running 1.2 head? Just asking.
- mcav 16y agoYes, many are running 1.2. This indicates that 1.2 is nearing completion.
- technomancy 16y agoIt's nice to be able to get off snapshots is the main thing. I don't want a stable version of Leiningen 1.2 depending on some random Clojure snapshot. Plus now the primitives work can get merged to master.
- jmatt 16y agoI recommend using 1.2 head. Even if you are learning clojure I'd recommend 1.2 head. With clojure, unlike most other languages, using head is relatively easy, it's stable and faster and it has more features. Pretty much a win from most perspectives. As soon as put a minimum amount of effort into researching or learning clojure you'll likely switch anyways. I think I switch after about five hours.
- tmountain 16y agoCongrats to the team! My favorite language just keeps getting better.
- 45g 16y agoI wonder if someone wants to port the type checker of Typed Racket over to Clojure?
- yason 16y agoUh. Once again the time to find out how to setup Clojure + Slime + swank clojure + clojure-mode this time. It's not that I didn't love the language, it's just that the installation is a PITA and generally not something I'd look forward to.
- poobox 16y agoIf you have gotten it working I have yet to find a decent walk through that works for 1.2 and would love some help getting things set up myself. I had hoped I could just use old-fashioned inferior-lisp with slime and clojure.main but that isn't working for me now either.