Scala 3 is a game changer in terms of compatibility in the Scala ecosystem that will greatly improve the day-to-day experience of every Scala programmer. This new compatibility era starts with the migration.
Moving from Scala 2 to Scala 3 is a big leap forward. Scala 3 is a shiny new compiler, built upon a complete redesign of the core foundations of the language. Yet we claim the migration will not be harder than before, when we moved from Scala 2.12 to Scala 2.13.
It will even be simpler in some respects, thanks to the interoperability between Scala 2.13 and Scala 3.
This chapter details the level of compatibility between the two versions at the different stages of the program. This is where you will find answers to the following questions:
- Is Scala 3 a different language?
- How hard is it to translate a Scala 2.13 project into Scala 3?
- Can we use a Scala 2.13 library in Scala 3?
- Inversely, can we use a Scala 3 library in Scala 2.13?
- Is it safe to deploy a Scala 3 program in a production environment?
- How fast are Scala 3 programs compared to Scala 2.13?
- Will my Scala 2.13 project be affected by the replacement of the Scala 2 macro feature?
- How can I port my Scala 2.13 macro library to Scala 3?
Contributors to this page:
Contents
- Compatibility Reference
- Source Level
- Classpath Level
- Runtime
- Metaprogramming
- Tour of the Migration Tools
- Scala 2 with -Xsource:3
- Scala 3 Migration Mode
- Migration Tutorial
- Prerequisites
- Porting an sbt Project (using sbt-scala3-migrate)
- Porting an sbt Project (by hand)
- Cross-Building a Macro Library
- Mixing Scala 2.13 and Scala 3 Macros
- Scala 3 Syntax Rewriting
- Incompatibility Table
- Syntactic Changes
- Dropped Features
- Contextual Abstractions
- Other Changed Features
- Type Checker
- Type Inference
- Compiler Options
- Compiler Options Lookup Table
- New Compiler Options
- Scaladoc settings compatibility between Scala2 and Scala3
- Compiler Plugins
- Kind Projector Migration
- External Resources