Skip to content

Commit 47f2f13

Browse files
alvinjb-studios
authored andcommitted
Incoporated @sjrd’s comments
1 parent 42041c0 commit 47f2f13

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

_overviews/scala3-book/tasty-for-end-users.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -116,12 +116,12 @@ TODO: These lines mostly come from https://www.scala-lang.org/blog/2018/04/30/in
116116
- The compiler uses it to support separate compilation.
117117
- The Scala _Language Server Protocol_-based language server uses it to support hyperlinking, command completion, documentation, and also for global operations such as find-references and renaming.
118118
- Tasty makes an excellent foundation for a new generation of reflection-based macros.
119-
- A build tool can use it to cross-build on different platforms and migrate code from one binary version to another.
120119
- Optimizers and analyzers can use it for deep code analysis and advanced code generation.
121120

122-
There’s one more big benefit:
121+
In a related note, Scala 2.13.4 has a TASTy reader, and the Scala 3 compiler can also read the 2.13 “Pickle” format. The [Compatibility Reference](https://scalacenter.github.io/scala-3-migration-guide/docs/compatibility.html) in the Scala 3 Migration Guide summarizes the benefits of this cross-compiling capability:
123122

124-
- Because the Scala 2.13.4 compiler can read Tasty files, and the Scala 3 compiler can read Scala 2.13 class files, you can intermix Scala 3 and Scala 2.13 code in the same project.
123+
>“You can have a Scala `2.13.4` module that depends on a Scala `3.0.0-M1` module, and the latter can even depend on another Scala `2.13.4` module. >Cross-compatibility will not restrain you from using the exciting new features of Scala 3.0.
124+
>In short, we have backward and forward compatibility and so migration can happen gradually and in any order.”
125125
126126

127127

0 commit comments

Comments
 (0)