This was mentioned in this thread, but it’s worth repeating … Scala
3.x works like a tranzitive dependency, so libraries can force a minimum
Scala version on downstream users. Projects depending on Pekko will be
forced to use at least Scala 3.3. This was, I believe, the original
purpose of LTS versions: to have have some stability in the Scala 3.x
versions that library authors are forcing on unsuspecting downstream
users.
I believe the consensus in the community is that libraries should depend
on Scala 3.3, for stability, but also because they added some features
from Scala 2, making it more production-ready. So depending on it is
fine, good job 👍
Pekko will be in a dilema at the next LTS. I suspect that upgrading
Scala 3 versions won’t be a problem, as long as forcing versions on
downstream users doesn’t break their build. Furthermore, Pekko may not
have a choice in upgrading, given its dependencies may upgrade, forcing
an upgrade in Pekko, too. It will be fun to see how it works out in
practice.
On 30 May 2023, at 13:37, Matthew Benedict de Detrich wrote:
One other note which I came up with recently and I believe is very
important to note is what the LTS part of Scala 3.3 means. LTS just
stands
for Long Term Support so it can mean different things in different
projects
but as mentioned here
https://github.com/lampepfl/dotty/issues/17330#issuecomment-1568161371,
in
the context of Scala 3 it actually means that **ANY** bug fix that
doesn't
break backwards and forwards compatibility will get backported to
Scala 3.3
LTS.
This is actually incredibly good news for the long term sustainability
of
Scala 3 support in Pekko and its modules.
On Wed, May 24, 2023 at 4:35 PM Matthew Benedict de Detrich <
[email protected]> wrote:
I would like to report that Scala 3.3 has been successfully merged
into
Pekko!
--
Alexandru Nedelcu
https://alexn.org
