{"id":558039,"date":"2025-04-16T14:05:20","date_gmt":"2025-04-16T13:05:20","guid":{"rendered":"https:\/\/blog.jetbrains.com\/?post_type=scala&p=558039"},"modified":"2025-04-17T08:16:14","modified_gmt":"2025-04-17T07:16:14","slug":"intellij-scala-plugin-2025-1-is-out","status":"publish","type":"scala","link":"https:\/\/blog.jetbrains.com\/ru\/scala\/2025\/04\/16\/intellij-scala-plugin-2025-1-is-out","title":{"rendered":"IntelliJ Scala Plugin 2025.1 Is Out!"},"content":{"rendered":"\n

Support for new features in Scala 3<\/h2>\n\n\n\n

Context Bounds and Givens<\/h3>\n\n\n\n

Scala 3.6 introduced a new syntax for context bounds and givens. You can read more about it in SIP-64<\/a>. In short, before Scala 3.6, it was impossible to name the context bound in the same place where it was defined. The way to do it was to introduce an implicit parameter, which resulted in awkward syntax, e.g. def reduce[A](xs: List[A])(using m: Monoid[A]): A introduced the context bound Monoid[A] as m. In the new syntax, it’s possible to simply write def reduce[A: Monoid as m](xs: List[A]): A and IntelliJ IDEA with the Scala plugin recognizes it and supports it.<\/p>\n\n\n\n

In a similar vein, we now support the recent changes in the given syntax.<\/p>\n\n\n\n

\"Three
Three old ways to declare and name a context bound vs the new syntax<\/em><\/figcaption><\/figure>\n\n\n\n
\"Multiple
Multiple context bounds<\/em><\/figcaption><\/figure>\n\n\n\n
\"Solving
Solving an old issue of a forward declaration of a context bound<\/em><\/figcaption><\/figure>\n\n\n\n

<\/p>\n\n\n\n

Named Tuples<\/h3>\n\n\n\n

Scala 3.7 brings the stabilization of Named Tuples and IntelliJ IDEA 2025.1 with the Scala Plugin already supporting them. In the new release, apart from simply recognizing the syntax for Named Tuples, we also support them in pattern matching, when you can both match against a given value of one of the tuple\u2019s fields, and extract that value to a new reference. On top of that, Scala 3.7 comes with a new way to extract a field value from a case class or a class with a customized unapply method that returns a named tuple. Until now, we could either use the underscore to mark all the fields we were not interested in when calling the unapply, or we could assign a whole class instance to a reference and then access the field we wanted through that reference.  Now, it\u2019s possible as well to simply name the fields we are interested in and assign their values to new references.<\/p>\n\n\n\n

You can read more about Named Tuples in SIP-58<\/a>.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Refutable patterns in for-comprehensions<\/h3>\n\n\n\n

Since Scala 3.4, refutable patterns (i.e., patterns that might not match) in for-comprehensions must be preceded by the case<\/code> keyword, or an error is reported. The new syntax helps recognize those cases.<\/p>\n\n\n\n

The debugger<\/h2>\n\n\n\n

We fixed a bug in Scala 2.13.3 where the debugger didn’t stop on breakpoints inside lazy vals in try\/catch blocks, and another, similar, when the debugger sometimes had trouble stopping at breakpoints inside lambdas in a trait.<\/p>\n\n\n\n

sbt<\/h2>\n\n\n\n

We made several improvements to the new separate production\/test modules. A new “Generate sbt managed sources” action helps avoid situations when good code is red because it relies on sources generated during the project import. On top of that, the “New Project” wizard now suggests downloading the JDK for a new sbt project, and we don’t show anymore the banner “No Scala SDK in module” when at the same time we offer to simply load the sbt project, which will automatically setup SDK.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Code highlighting and inlay hints<\/h2>\n\n\n\n

In the 2024.3 release, we introduced support for transparent inline methods in Scala 3. Now, as we continue to work on support for Scala macros, we offer support for Scala 2 macro types. Also, we improved type hints for variable patterns, generators, and literal parameters, as well as type info for underscore parameters and kind projector syntax. The X-Ray mode was enhanced as well: you can now enable parameter name hints for all parameters, not only literals, and see when the apply method is being used, instead of an ordinary constructor.<\/p>\n\n\n\n