However, these compiler upgrades turn out to be not safe. The code base of the compiler changes extensively, and our code becomes deprecated and sometimes incompatible with that changes. For instance, one of that incompatibility was found in Typers.scala and solved by a stub exception throw.
Also, due to the change in the Scala version number from 2.11.0 to 2.11.2 (don't know why don't they set 2.11.5), all the Gradle projects won't run now. In order to run them, this line in the build.gradle:
compile 'org.subscript-lang:scala-library:2.11.0'
should be changed to this:
compile 'org.subscript-lang:scala-library:2.11.2'
In general, we should move to parboiled asap, since other things may well also go wrong during such compiler upgrades without our knowledge yet.
However, these compiler upgrades turn out to be not safe. The code base of the compiler changes extensively, and our code becomes deprecated and sometimes incompatible with that changes. For instance, one of that incompatibility was found in Typers.scala and solved by a stub exception throw.
Also, due to the change in the Scala version number from 2.11.0 to 2.11.2 (don't know why don't they set 2.11.5), all the Gradle projects won't run now. In order to run them, this line in the
build.gradle:compile 'org.subscript-lang:scala-library:2.11.0'should be changed to this:compile 'org.subscript-lang:scala-library:2.11.2'In general, we should move to parboiled asap, since other things may well also go wrong during such compiler upgrades without our knowledge yet.