Apply suggestions from code review

Co-authored-by: Seth Tisue <[email protected]>
Co-authored-by: Jamie Thompson <[email protected]>

Author: 3 people

blog/_posts/2024-02-26-scala-3.4.0-and-3.3.2-released.md

@@ -10,17 +10,17 @@ We are thrilled to announce the release of two versions of Scala 3: the first ve
 
 Scala 3.4.0 code can use dependencies compiled with Scala 3.3.x, but not the other way around. That means that if you are a library author, you should consider staying on the LTS line. If you are working on a project that is not meant to be used as an external dependency, feel free to update to Scala 3.4.0, especially if you are starting a new project.
 
-Scala 3.4.0 and 3.3.2 share most of the changes since the 3.3.1 version. The difference Scala 3.4.0 adds new features and deprecates legacy mechanisms, while version 3.3.2 is focused solely on bug fixes and usability improvements. What's more, 3.3.2, as a part of the LTS line, maintains not only full output compatibility but also full source compatibility. **This means that every single one from over a thousand projects we checked that worked with 3.3.1 still work with 3.3.2.** To achieve this, we had to be extra careful with selecting changes for that release. Thus, not every bug that is fixed in 3.4.0 is also fixed in 3.3.2. Some of the not-ported changes might still land in 3.3.3.
+Scala 3.4.0 and 3.3.2 share most of the changes since the 3.3.1 version. The difference is that Scala 3.4.0 adds new features and deprecates legacy mechanisms, while version 3.3.2 is focused solely on bug fixes and usability improvements. What's more, 3.3.2, as a part of the LTS line, maintains not only full binary compatibility but also full source compatibility. **We checked that every single one of over a thousand projects that worked with 3.3.1 still work with 3.3.2.** To achieve this, we had to be extra careful with selecting changes for that release. Thus, not every bug that is fixed in 3.4.0 is also fixed in 3.3.2. Some of the not-ported changes might still land in 3.3.3.
 
 ## What's new in 3.3.2 LTS (and 3.4.0 too)
 
-If you go through the release notes of Scala [3.3.2 LTS](https://github.com/lampepfl/dotty/releases/tag/3.3.2), you can see a lot of bug fixes. One area that received special attention in that regard was coverage support. With most pains fixed, we are now confident in the state of coverage.
+In the release notes of Scala [3.3.2 LTS](https://github.com/lampepfl/dotty/releases/tag/3.3.2), you can see a lot of bug fixes. One area that received special attention in that regard was coverage support. With most pains fixed, we are now confident in the state of coverage.
 
 Another important change, not directly visible to end users, is the integration of the presentation compiler into the compiler itself. This makes building tooling easier and allows for a more stable and reliable user experience when using Metals.
 
 ## Changes exclusive to 3.4.0
 
-Release notes of [3.4.0](https://github.com/lampepfl/dotty/releases/tag/3.4.0) contains a lot of substantial changes in improvements. Most noteworthy of them can be grouped in a few broad categories.
+Release notes of [3.4.0](https://github.com/lampepfl/dotty/releases/tag/3.4.0) contains many substantial changes and improvements. The most noteworthy can be grouped in a few broad categories:
 
 ### Stabilized SIPs
 
@@ -58,7 +58,7 @@ Release notes of [3.4.0](https://github.com/lampepfl/dotty/releases/tag/3.4.0) c
   ```
 
   will have its return type correctly inferred as `(List[T], List[T])`. Earlier, it would result in a rather unintuitive type error.
-- The compiler now avoids generating given definitions that loop, removing long-standing footgun of implicit resolution.
+- The compiler now avoids generating given definitions that loop, removing a long-standing footgun in implicit resolution.
 
 ### Backend improvements
 
@@ -67,6 +67,17 @@ Release notes of [3.4.0](https://github.com/lampepfl/dotty/releases/tag/3.4.0) c
 
 ### Reporting
 
+- Scala 3.4 improves the error message when a signature from the classpath comes from an incompatible TASTy version. It has improved readability and provides a more useful diagnostic of what a user can do to fix the problem.
+  ```
+  error while loading Tuple,
+    TASTy file /scala/Tuple.tasty could not be read, failing with:
+    Forward incompatible TASTy file has version 28.4, produced by Scala 3.4.0,
+    expected stable TASTy from 28.0 to 28.3.
+    To read this TASTy file, use a Scala 3.4.0 compiler or newer.
+    Please refer to the documentation for information on TASTy versioning:
+    https://docs.scala-lang.org/scala3/reference/language-versions/binary-compatibility.html
+  ```
+
 - If there is an error reading a class file, we now report the version of the classfile and a recommendation to check JDK compatibility:
 
   ```
@@ -78,7 +89,7 @@ Release notes of [3.4.0](https://github.com/lampepfl/dotty/releases/tag/3.4.0) c
   ```
 
   This will improve the user experience when the class file format changes unexpectedly. This feature will be backported to Scala 3.3.3.
-- Progress reporting of compilation is now visible in IDEs. Metals IDE users will notice that compilation progress is no longer frozen at 0% when using sbt or bloop as the BSP server. IntelliJ will also correctly report progress for BSP and sbt based projects
+- Progress reporting of compilation is now visible in IDEs. Metals IDE users will notice that compilation progress is no longer frozen at 0% when using sbt or bloop as the BSP server. IntelliJ will also correctly report progress for BSP and sbt based projects.
 
 ### Experimental changes
 
@@ -94,9 +105,9 @@ Following syntax is now deprecated and will report warnings when used:
 - `var x = _` (rewrite to `var x = scala.compiletime.uninitialized`)
 - `with` as a type operator (rewrite to `&`)
 - `xs: _*` varargs (rewrite to `xs*`)
-- trailing `_` to force eta expansion (can be just ommitted)
+- trailing `_` to force eta expansion (can be just omitted)
 
-All those rewrites will be performed automatically by the compiler if we run it with `-rewrite -source 3.4-migration` flags.
+All those rewrites will be performed automatically by the compiler if you run it with `-rewrite -source 3.4-migration` flags.
 
 ### Other source compatibility concerns
 
@@ -124,11 +135,11 @@ All those rewrites will be performed automatically by the compiler if we run it
   import scala.language.`3.3`
   ```
 
-  alternatively, the definition can be changed to `transparent inline`, but as this is a TASTy breaking change, it is not a default recommendation. (Also, `inline` should be preferred when possible over `transparent inline` for reduced binary size)
+  alternatively, the definition can be changed to `transparent inline`, but as this is a TASTy breaking change, it is not a default recommendation. (Also, `inline` should be preferred when possible over `transparent inline` for reduced binary size.)
 
 ## Contributors
 
-Thank you to all the contributors who made the release of 3.4.0 and 3.3.2 LTS possible
+Thank you to all the contributors who made the release of 3.4.0 and 3.3.2 LTS possible!
 
 According to `git shortlog -sn --no-merges 3.3.1..3.4.0` these are: