News for hackers. Stuff that matters.
Re:Clojure vs. Scala by octo_t on Tuesday December 24, 2013 @08:01AM (#6959230)
How are collections broken? Views are deprecated/set to be deprecated, I don't really use scala.io, I find java io sufficient for my needs, scala.xml is being split out in 2.11 and macros will let people use a third party implementation, scala.actors is also deprecated, having been replaced by Akka.

Paul has definitely found a lot of "bugs", he has certainly contributed a huge amount to the cleanliness of the code base, and has been a big pusher for removing certain levels of unsoundness in the type system, but if you were looking for bug-finders + fixers, Simon Ochsenreither is probably a better bet.

Re:Clojure vs. Scala by Hakeashar on Tuesday December 24, 2013 @09:43AM (#6959498)
Just a quick question - if the views are set to be deprecated, what would be the way to do a (long) series of collection transformation without spawning multiple intermediate collections? So, essentially, equivalent of .view, transformations, .force?
Re:Clojure vs. Scala by profdemarco on Tuesday December 24, 2013 @09:49AM (#6959525)
You use an iterator, which has its own caveats, or you simply accept that chaining collection transformations is going to be ridiculously inefficient.