3 ms·

There is no "dropping" except if you assume that Scala 2.11 will just disappear tomorrow. I don't get the whole dooms day scenario. - Google is working on Jav

There is no "dropping" except if you assume that Scala 2.11 will just disappear tomorrow. I don't get the whole dooms day scenario. - Google is working on Java 8 support. - The current version of Scala supports the current Android stack. - Depending on the timing, the next version of Scala might also support the then-current Android stack. - You can always use Scala-for-Android (aka 2.11). Just think of it as a flavor like Scala-JVM, Scala.js or Scala-Native.

lmm 10y ago
Fair enough, but there are bugs/missing features in Scala 2.11 that I want fixed, and they're going to be fixed in Scala.js and Scala-Native so it would be a real shame if they weren't fixed in Scala-for-Android at the same time.
- premium-concern 10y ago
  Which ones?
  - lmm 10y ago
    The usual ones, I'm sure. Poor syntax for type lamdbas. Unification across kinds (hopefully possibly going to be backported to 2.11). All the ways of expressing union types (or indeed basic enums) are a bit clunky. Irrefutable patterns in for/yield constructs compile to a silly withFilter call. PartialFunction/Function having the wrong subtyping relationship. mapValues being lazy when all the other functions on the same interface are strict. Stream implementing the collection interface. More than anything specific though, I don't want to be stuck on an old version as the language moves forward.
    - premium-concern 10y ago
      Huh? None of that will be in 2.12 except unification, and that's already planned for backporting to 2.11 (and you can just use the compiler plugin until then). > I don't want to be stuck on an old version as the language moves forward. How are you going to be stuck? You might need to stay on 2.11 a bit longer until Google gets their shit together. Most likely this will be during 2.12. Sure, you might miss the first few minor releases of 2.12 ... but stuck?
      - lmm 10y ago
        Where are you getting this confidence that Google will "get their shit together" quickly, or ever? I can easily imagine Google not shipping Java 8 for as long as Oracle remains in business.

lmm 10y ago

Fair enough, but there are bugs/missing features in Scala 2.11 that I want fixed, and they're going to be fixed in Scala.js and Scala-Native so it would be a real shame if they weren't fixed in Scala-for-Android at the same time.

premium-concern 10y ago
Which ones?
- lmm 10y ago
  The usual ones, I'm sure. Poor syntax for type lamdbas. Unification across kinds (hopefully possibly going to be backported to 2.11). All the ways of expressing union types (or indeed basic enums) are a bit clunky. Irrefutable patterns in for/yield constructs compile to a silly withFilter call. PartialFunction/Function having the wrong subtyping relationship. mapValues being lazy when all the other functions on the same interface are strict. Stream implementing the collection interface. More than anything specific though, I don't want to be stuck on an old version as the language moves forward.
  - premium-concern 10y ago
    Huh? None of that will be in 2.12 except unification, and that's already planned for backporting to 2.11 (and you can just use the compiler plugin until then). > I don't want to be stuck on an old version as the language moves forward. How are you going to be stuck? You might need to stay on 2.11 a bit longer until Google gets their shit together. Most likely this will be during 2.12. Sure, you might miss the first few minor releases of 2.12 ... but stuck?
    - lmm 10y ago
      Where are you getting this confidence that Google will "get their shit together" quickly, or ever? I can easily imagine Google not shipping Java 8 for as long as Oracle remains in business.