meisam
commented
2 years ago I investigated this issue a bit and I have a hunch why it might be happening. It looks like ScalaWorker3.java, which is the class that packs the arguments for the Scala3 compiler and calls the compiler, is called with Scala2 libraries.
To be more specific, if I patch ScalaWorker3.java and print the ScalaVersion during the build, i get scala version: 2.13.5.
diff --git a/src/java/io/bazel/rulesscala/scalac/ScalacWorker3.java b/src/java/io/bazel/rulesscala/scalac/ScalacWorker3.java
index 370be29..ef136ee 100644
--- a/src/java/io/bazel/rulesscala/scalac/ScalacWorker3.java
+++ b/src/java/io/bazel/rulesscala/scalac/ScalacWorker3.java
@@ -4,0 +5 @@ import scala.Tuple2;
+import scala.util.Properties;
@@ -75,0 +79 @@ class ScalacWorker3 implements Worker.Interface {
+ System.out.println("scala version: " + Properties.versionNumberString());The compiler runs in the same process as ScalaWorker3.java, it is just a call to the doCompile method:
Compiler compiler = driver.newCompiler(r._2);
Reporter reporter = driver.doCompile(compiler, r._1, r._2);It makes sense that a new process is not spawn for each new compile task, so pay the startup and warmup cost of the scala compiler once, but it sounds like the reported scala version at runtime should match the expected scala3 version.
Cats-effect is an involved library and exercises advanced features in the scala compiler. I thinks that's why this crash does not happen with all the libraries.
I'll do more tests and report the findings.
fabianhjr
WojciechMazur
Steps to reproduce the crash:
The Scala3 compiler, dotty, crashes with: