If you're in London today, join us on the London Scala meetup. We'll be talking about how Metals can help you will large Scala and Java codebases.
There will also be a great presentation on real life crashes in production.
See you there!
www.meetup.com/london-scal...
New Metals 1.6.6 is out!
- Allow users to view the output of `-explain`
- Standalone MCP server
- Option to automatically shut down Bloop
- Support for Play Twirl templates
- Improvements to new file creation
Learn more at scalameta.org/metals/blog...
Take a quick 5โminute survey that directly impacts Scalaโs roadmap, libraries, and tooling. This short survey evaluates Scala adoption and usage among developers.
Scala Survey 2026 is brought to you by VirtusLab and Scala Center.
virtuslab.typeform.com/ScalaSurvey...
If you're interested in Scala 2 and Scala 3 compatibility, what TASTy is, and how it fits into the whole story, take a look at this blog post by Wojciech Mazur.
scala-lang.org/blog/state-...
sttp-ai now supports #Scala Native!
You can use: OpenAI, Claude, Grok, Ollama, ...
With different flavours of Scala: direct, functional, Future-based
On various platforms: JVM & Native
(not all combinations are supported, though)
Enjoy :)
If you donโt specify a port, a random one will be usedโunless the server has already run in the workspace. In that case, it will try to reuse the same port (if available).
We still donโt support the stdio option, but if anyone is interested in having it implemented, let us know!
Next, you can run the generated executable JAR from within your workspace, or specify the full path using the `--workspace` argument.
You can also use the `--client` option. For all known MCP clients, it will try to automatically create the required configuration entries.
In the upcoming Metals version, youโll be able to start it standalone as an MCP server! You can already try it out in two steps:
First, bootstrap your executable JAR using Coursier.
The new release is out, removing all references to the old Sonatype snapshot repositories. Let us know if you encounter any issues! github.com/VirtusLab/s...
x.com/ScalaSpace/...
๐ Join us at the Wrocลaw Scala User Group Meetup (#17) on Feb 24 in Wrocลaw!
๐ Where: Hard Rock Cafe Wrocลaw, ul. Rynek 25
๐
When: Tuesday, Feb 24 โข 6:00 PM โ 8:00 PM CET
๐ RSVP here: www.meetup.com/wroclaw-sca...
See you there! ๐
#Scala #Meetup #Wroclaw #TechCommunity #SoftwareEngineering
We are working on a new release of Scala CLI that removes any mention of the old snapshot repositories.
We are working on a fix, but the current workaround is to download the dependency before running Scala CLI as in the attached picture or use the '--server=false' flag.
There is currently an issue with Scala CLI, which might cause it to hang on downloading needed dependencies. This is caused by a problem with the old Sonatype snapshot repositories. For example, s01.oss.sonatype.org/content/rep...
Let the maintainers know if you're interested! It's all open source on github.com/computenode...
If you are using MacOS you will need to add two more dependencies to you Scala CLI file.
If you ever wanted to easily program on GPU with Scala in a functional way, your wait is over! Read more about on cyfra.computenode.io/
Hey, #ScalaCLI v1.12.1 is out! The changes include:default Scala version changed to 3.8.1default Scala Native version changed to 0.5.10a number of fixes, internal changes and dependency bumps,Be sure to check the release notes here: github.com/VirtusLab/s...
As a side note, if you ever need build-time information in your script, you can achieve this with the 'buildInfo' using directive!
The new Scala Native release is here! Check it out: github.com/scala-nativ...
This update includes numerous bug fixes, including one that affects Scalafmt's native binaries.
๐ข Ready to try Scala 3.8?
Full release notes: www.scala-lang.org/news/3.8/
โ ๏ธ Use 3.8.1 (not 3.8.0) โ a runtime regression was identified and fixed.
#Scala #Programming #FunctionalProgramming
๐ฎ What's next?
Scala is now in feature freeze for 3.9 LTS, which will be focused on stability & bug fixes.
Your 3.8 code will work on 3.9 without changes.
Scala 3.8.2 stable expected Feb 2026.
Experimental SIP-75: Single-line lambdas after colon
- You can read `:` uniformly as โapplicationโ when it is followed by either an indented block or a lambda.
- it becomes much easier to switch between styles
๐ฌ Experimental: Match with sub-cases.
Experimental extension to pattern matching: a `case` in a `match` can be followed by a nested "sub-match" introduced by the `if` keyword.
This feature enables you to:
If sub-case doesn't match outer match will continue!
Experimental SIP-70: Flexible Varargs introduced
SIP-70 removes a long-standing limitation of Scala varargs calls: you can now use `*` (spread) more than once in a single argument list.
No more manual concatenation!
SIP-71: New into keyword for implicit conversions is now available for preview.
Scala 3 previously would require `import scala.language.implicitConversions` anywhere you *use* `scala.Conversion` instances implicitly.
SIP-57: runtimeChecked is now stable.
It enables you to opt-out of certain static checks and defer them to runtime without resorting to the older, syntactically awkward `: @unchecked` type ascription.
Perfect for chained calls!
SIP-62: Better Fors is now stable & enabled by default.
Two key improvements are:
- Aliases allowed before generators.
- No unnecessary map calls.
๐ฅ๏ธ The REPL got a major upgrade!
It's now powered by fansi + pprint. It will also try to skip packages where aplicable to shorten previously long expressions.
Repl is also separate artifact now โ it will be easier to embed in your tools but might require some work in the existing ones.
๐ The standard library is now compiled with Scala 3.
This is a stepping stone toward Scala 3 having its own stdlib (starting in 3.10).
โ ๏ธ Minor source change: context bounds now desugar to given, requiring using.
โ ๏ธ JDK 17 is now required for compiling Scala 3.
This change prepares Scala for JDK 26+, which restricts sun.misc.Unsafe. The new lazy vals implementation uses VarHandles instead.
