Skip to content

Commit 5813c8a

Browse files
committed
Add info about percentage of libraries affected by source incompatibilities in 3.2
1 parent 1b5147c commit 5813c8a

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

blog/_posts/2022-08-05-long-term-compatibility-plans.md renamed to blog/_posts/2022-08-17-long-term-compatibility-plans.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -36,8 +36,7 @@ We believe that you should treat the compiler as one of your dependencies. If yo
3636

3737
If you are a library author following the semantic versioning, we advise you to introduce new minor versions of the compiler only in minor releases of your library. New patch versions of the compiler can be introduced anytime, as they are forward and backward compatible.
3838

39-
That may be surprising if you have experience developing libraries for Scala 2. For example, migrating any codebase from 2.11 to 2.12 was a huge undertaking. Since they were not output-compatible, most libraries needed to resort to cross-compilation to support both versions. Thanks to the guarantees of Scala 3, there is no longer a need for cross-compilation. For example, the migration from Scala 3.1 to Scala 3.2 for the large majority of the projects would only require changing the version in the build definition.
40-
// TODO: PUT HERE THE EXACT PERCENTAGE OF PROJECTS THAT WILL BE AFFECTED BY THE SOURCE INCOMPATIBILITIES BETWEEN 3.1 AND 3.2
39+
That may be surprising if you have experience developing libraries for Scala 2. For example, migrating any codebase from 2.11 to 2.12 was a huge undertaking. Since they were not output-compatible, most libraries needed to resort to cross-compilation to support both versions. Thanks to the guarantees of Scala 3, there is no longer a need for cross-compilation. For example, the migration from Scala 3.1 to Scala 3.2 for the large majority of the projects would only require changing the version in the build definition. We have tested 900 Scala libraries that were passing compilation using 3.1.3. Out of them, only 13 failed to compile with 3.2.0. That means that for 98.6% of the libraries changing the compiler version to 3.2.0 does not require a single change in the source code.
4140

4241
## The problem
4342

0 commit comments

Comments
 (0)