Lazy Values: It allows defining lazy value declarations using the new modifier lazy.Existential Types: It allows defining existential types using the new keyword forSome.Refined Pattern Matching Anonymous Functions: It is now possible to use case clauses to define a function value directly for functions of arities greater than one.īelow are the changes that went towards the 2.6.0 version,.Implicit Anonymous Functions: It is now possible to define anonymous functions using underscores in the parameter position.It will be deprecated in future versions. For-Comprehensions, Revised: Change in the syntax of for-comprehensions.Early Object Initialization: It allows initializing some fields of an object before any parent constructors are called.Below are some of the main features in this version,
#SCALA VERSION SOFTWARE#
The rest of the world simply accepted: libraries stay on current LTS (see Java libs and JVM versions), or write "experimental" or "bleeding edge" in their abstract, app code might use latest version to consume all older versions while having access to all the bugfixes.Web development, programming languages, Software testing & others Scala Versionsīelow are all the versions in Scala up to date and with the main features in all the versions: VERSION 2.5.0Ģ.5.0 was released around May 2007.
The fact that we need to cross compile for 2.11/2.12/2.13/3 is an abomination that nobody else does and we have the reasons to believe that it hurts Scala adoption. It would help after 3.2 is released then next version of 3.1 gets ability to read 3.2 TAST. Then same problem will shift to 3.1/3.2 after some time. And if you made it compile on 3.1.y there is no incentive for you to compile it twice: once for 3.1.y and 3.2.x, since Tasty would be the same. If your code use feature introduced in 3.2.x, it doesn't make sense to cross compile it with 3.1.y because it would not compile on 3.1.y. And for app code you can always use the latest version. Which is why it is encouraged that library maintainers use the lowest version they need for now and LTS version in the future. You are forced to use 3.1 too and it will make your library incompatible with rest of app using 3.0. The TASTy file was produced by Scala 3.1.3-bin-nonbootstrapped.Īnd if Scalatest is compiled with 3.1 you can't use it with 3.0 cross compile. This TASTy file was produced by a more recent, forwards incompatible release. class file scala/runtime/$throws$package.class is broken, reading aborted with class Setting Scala version to 3.0.2 on 2 projects. What is situation between 3.2 and 3.1? Can 3.1 read library compiled by 3.2? If you have one library compiled by scala3.1 it means you can't use scala 3.0. I don't understand how it is improvement over 2.X where every version has its own JARs.
It seems that scalatest JAR is compiled with 3.1 which 3.0 can't read. Problem is that in Scala 3, every scala sub version seems to compile to one _3 JAR and they are incompatible. LibraryDependencies += "org.scalatest" %%% "scalatest" % "3.2.14" % "test" Want your library here? Message the moderators! Open Source Applications written in Scala Introduction to Programming with Dependent Types in Scala (advanced).Functional Programming Principles in Scala.Functional Programming in Scala (Manning).Scala Center (not-for-profit scala org).Try Scala Online with Scastie or ScalaFiddle.
0 kommentar(er)
