| 10 Apr 2024 |
|  bumblebread. joined the room. | 22:59:04 |
| 11 Apr 2024 |
|  arturaz changed their profile picture. | 09:31:24 |
|  davesmith00000 changed their profile picture. | 10:23:05 |
| 12 Apr 2024 |
|  fel_mazo joined the room. | 09:25:33 |
|  nphardass joined the room. | 11:25:18 |
| 14 Apr 2024 |
|  sumew joined the room. | 15:49:18 |
| 15 Apr 2024 |
|  valencik changed their profile picture. | 12:31:42 |
| 16 Apr 2024 |
|  wu_lynx joined the room. | 15:44:28 |
|  jackkoenig changed their profile picture. | 20:29:15 |
|  andy.czerwonka joined the room. | 23:17:41 |
| 17 Apr 2024 |
|  ashwin1899 joined the room. | 07:25:43 |
 oclok_ | Hello. Good day!
We are using scala version 2.12.10 in our project. And I see the following message in Metals Doctor: Scala 2.12.10 is no longer supported by Metals, to get the best support possible it's recommended to update to at least 2.12.18.
Is it mandatory to upgrade to supported versions? | 13:07:14 |
 Tomasz Godzik | It's not, but we stop publishing bugfixes and new features for older versions | 13:08:19 |
| Tomasz Godzik | Why not update to 2.12.18 | 13:08:29 |
| Tomasz Godzik | There is a lot of improvements and probably some security fixes | 13:08:49 |
| oclok_ | We had to resolve some other dependencies which are dependent on 2.12.10, that's why we thought of sticking to 2.12.10 instead of 2.12.18.
And by the when I see the following Warning when I try to run a configuration using 2.12.10:
2024.04.17 18:44:51 WARN Cannot fetch expression compiler of Scala 2.12.10: Error downloading ch.epfl.scala:scala-expression-compiler_2.12.10:4.0.4
not found: /Users/localuser/.ivy2/local/ch.epfl.scala/scala-expression-compiler_2.12.10/4.0.4/ivys/ivy.xml
not found: https://repo1.maven.org/maven2/ch/epfl/scala/scala-expression-compiler_2.12.10/4.0.4/scala-expression-compiler_2.12.10-4.0.4.pom | 13:17:15 |
| oclok_ | * We had to resolve some other dependencies which are dependent on 2.12.10, that's why we thought of sticking to 2.12.10 instead of 2.12.18.
And by the I see the following Warning when I try to run a configuration using 2.12.10:
2024.04.17 18:44:51 WARN Cannot fetch expression compiler of Scala 2.12.10: Error downloading ch.epfl.scala:scala-expression-compiler_2.12.10:4.0.4
not found: /Users/localuser/.ivy2/local/ch.epfl.scala/scala-expression-compiler_2.12.10/4.0.4/ivys/ivy.xml
not found: https://repo1.maven.org/maven2/ch/epfl/scala/scala-expression-compiler_2.12.10/4.0.4/scala-expression-compiler_2.12.10-4.0.4.pom | 13:19:02 |
| 18 Apr 2024 |
|  mzuehlke joined the room. | 06:39:00 |
| Tomasz Godzik | We had to resolve some other dependencies which are dependent on 2.12.10, that's why we thought of sticking to 2.12.10 instead of 2.12.18.
the whole line is binary compatible so there is no risk using a later version while your dependencies use an older one | 07:25:06 |
| Tomasz Godzik | it's the same case with expression compiler, we don't release for older versions | 07:26:07 |
|  emperorf joined the room. | 13:18:36 |
|  zanpreston joined the room. | 15:57:31 |
| 19 Apr 2024 |
 m.hughes | The compiler must have some internal map of type dependencies, yes? Like ClassA depends on ClassB, etc. Even better would be PackageA depends on PackageB. If so, is that information accessible in scalameta API anywhere? Ultimately I'm looking for some code analysis tool that will help me tease apart dependencies in my code base short of: 1) create submodule 2) move classes 3) see what breaks 4) fix, repeat. Ultimately submodules are my goal but for sanity sake, I'd like to be able to do these refactorings without restructuring the modules constantly as it's kind of painful with reloading SBT, bloop, metals, etc. | 13:53:41 |
| Tomasz Godzik | There is the Zinc Analysis, but that probably might a lot of work to deal with | 14:38:09 |
| Tomasz Godzik | I remember my colleague was actually working on something like that | 14:38:13 |
|  rodney0 changed their profile picture. | 17:05:48 |
| 22 Apr 2024 |
|  renghen joined the room. | 10:02:42 |
| m.hughes | Any idea on how to fix this error:
[OrganizeImports] Could not determine whether 'org' is fully-qualified because the symbol information is missing. We will continue processing assuming that it is fully-qualified. Please check whether the corresponding .semanticdb file is properly generated.
I have this in my build.sbt: ThisBuild / semanticdbEnabled := true
and this in my plugins: addSbtPlugin("org.scalameta" % "sbt-scalafmt" % "2.4.6")
addSbtPlugin("ch.epfl.scala" % "sbt-scalafix" % "0.11.0")
| 18:53:52 |
| 23 Apr 2024 |
 bjaglin | it's scalafix OrganizeImports indeed. It's been reported before (https://github.com/scalacenter/scalafix/issues/1245), but I could not reproduce the problem, so if you have a repro, I'd be glad to look at it m.hughes | 19:03:57 |
| 24 Apr 2024 |
|  digitalmechanic joined the room. | 10:26:54 |
