The SIP page has been cleaned up and now reflects all SIPs that have been shipped moving forward.
For SIPs that are currently in progress, or for which an experimental implementation exists in the compiler, please refer to the official SIP PR queue.
6 Likes
Should add some tags to the sip for which area and first shipped in which version
3 Likes
Indeed I see that it now takes v0.16.0, but it’s still failing, while locally and in my CI everything is fine. I opened an issue on the CB repo DFiant HDL failing in CB but not in CI or local? · Issue #597 · VirtusLab/community-build3 · GitHub
1 Like
The third RC is now availalable for testing - this version fixes some performance regressions and introduces bunch of major bugfixes.
Stable release for 3.8.0 is now planned for the first week of January.
7 Likes
Scala 3.8.0-RC4 is now available for tests
We’re already planning RC5 to be released next week with some of the last identified issues fixed.
6 Likes
Is it too late to get this fix by @lihaoyi into the 3.8.0 release?
It fixes an annoying error in REPL when pressing TAB the first time:
These would target 3.8.1, to be released in 6 weeks
1 Like
Scala 3.8.0-RC5 is now available for tests.
It syncs standard library sources with Scala 2.13.18, adds @uncheckedOverride support and fixes some of the found regressions/bugs.
7 Likes
The 3.8.0-RC6 is out!
This version fixes performance regression introduced to Map.keySet and ensures specialized classes copied from Scala 2.13 are not having attributes assigned that can be problematic for compiler or tooling.
We don’t expect RC7 to be needed, stable release is planned for the next wek
5 Likes
Do you have an estimate for when 3.8.1-RC1 might be released? @WojciechMazur
(I’m considering to perhaps go bleeding edge to access the REPL TAB completion fix for my Req. Eng. course starting soon 
)
1 Like
3.8.1-RC1 was already cutoff, it would be released together with 3.8.0 - so also next week (mostly so that we don’t have a confusing new RC before stable version of previous one)
2 Likes
Fantastic!
I think this bug is important. unfortunately, Scala 3.8.0 does not include a fix for it. SIP-62 better for `dropForMap` phase bug · Issue #24673 · scala/scala3 · GitHub
1 Like
The fix was not merged yet, we want to include fix for this problem in 3.8.1 (which would we plan to release as stable in ~4 weeks)
2 Likes
Scala 3.8 is out!
A runtime regression was detected after publishing Scala 3.8.0 artifacts. Please use Scala 3.8.1 instead.
The issue could lead to JVM linkage errors at runtime. It may have affected Scala 3 users who execute Scala 2.13 libraries, as well as certain uses of specialized members in the Scala standard library. Any library published with Scala 3.8.0 is expected to remain binary compatible. Artifacts built with Scala 3.8.0 are safe to use and should stay binary compatible with subsequent Scala 3 releases.
A more detailed postmortem will follow shortly after the Scala 3.8 release announcement.
13 Likes
Maybe it’s not a big deal, but I am saddened by the use of generative AI for the cover image
To me it looks cheap, and sends the message that artists are not welcome, or at least not needed in Scala
It seems to go against the spirit of talks that were given at Scala Days last year, for example:
And if the budget is too tight to pay an illustrator, designer, or photographer, then I would encourage you to reuse images you have commissioned in the past, for example the one used for at least versions 3.7 and 3.6 or a photograph of the BC stairs at EPFL (which inspired the logo)
(I have no proof you commissioned artists for both of these, but it seems fairly likely, if not then it really is a shame)
P.S: I am not trying to start a debate about it, or what constitutes art, I just want to share my opinion on the presentation of an update that seems in content very positive
6 Likes
.. the use of generative AI for the cover image
For which image? How do we know, that AI was used in its production?
IMHO, taking in account how much AI gets pushed and FOMO-ed on developers, usage of AI is not only possible, but expected.
1 Like
The one that tops the 3.8 release announcement page, i.e., this.
I agree that it feels cheap. Since a picture is not necessary at all, it’s better if it’s more clearly a positive.
1 Like
Yeah, I can admit that’s my fault - forgot to request one from our VL designers in time. We’ll be back with hand-crafted graphics in 3.9
8 Likes
It is very cool release and there is a nice picture 
IMHO: The real guilty is youtube. The amount of AI generated content is nasty big. I just have got an allergy to AI in youtube )