Skip to content

Commit 439ade5

Browse files
committed
Final polish for 3.4.0 announcement
1 parent 2f3b010 commit 439ade5

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

blog/_posts/2024-02-29-scala-3.4.0-and-3.3.3-released.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -98,13 +98,14 @@ Release notes of [3.4.0](https://github.com/lampepfl/dotty/releases/tag/3.4.0) c
9898

9999
This will improve the user experience when the class file format changes unexpectedly. This feature will be backported to Scala 3.3.3.
100100
- 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.
101+
- Diagnostics (including unused warnings) are now exported to SemanticDB. That will allow better handling of warnings in tooling. See [#17835](https://github.com/lampepfl/dotty/pull/17835)
101102

102103
### Experimental changes
103104

104105
- An experimental `@publicInBinary` annotation can mark definitions that should be treated as a part of binary API. It is useful where some protected or private-in-package definitions are used in the inlined code. When they are marked, it is harder to accidentally break the binary compatibility by doing seemingly harmless refactoring. If the accompanying `-WunstableInlineAccessors` linting option is enabled. There will be a warning about using things not marked as binary API in inlined code. Originaly it was presented in [SIP-52](https://docs.scala-lang.org/sips/binary-api.html).
105106
- `-experimental` compiler flags will mark all top-level definitions as `@experimental`. This means that the experimental language features and definitions can be used in the project. Note that this does not change the strong guarantees of the stability of the non-experimental code. The experimental features can only be used in an experimental scope (transitively). In 3.5, we plan to allow using this flag also in the stable releases of the compiler.
106107

107-
### Legacy syntax depreacations
108+
### Legacy syntax depreacation
108109

109110
Following syntax is now deprecated and will report warnings when used:
110111

@@ -153,7 +154,7 @@ or globally using the `-source 3.3` flag.
153154

154155
## Contributors
155156

156-
Thank you to all the contributors who made the release of 3.4.0 and 3.3.2 LTS possible!
157+
Thank you to all the contributors who made the release of 3.4.0 and 3.3.3 LTS possible!
157158

158159
According to `git shortlog -sn --no-merges 3.3.1..3.4.0` these are:
159160

0 commit comments

Comments
 (0)