Workaround for SI-9111

The inliner forces some method symbols to complete that would not be
completed otherwise. This triggers SI-9111, in which the completer of
a valid Java method definition reports an error in mixed compilation.

The workaround disables error reporting while completing lazy method
and class symbols in the backend.

2 files changed, 23 insertions, 0 deletions

diff --git a/test/files/pos/t9111-inliner-workaround/A_1.java b/test/files/pos/t9111-inliner-workaround/A_1.java
new file mode 100644
index 0000000000..bc60b68ea6
--- /dev/null
+++ b/test/files/pos/t9111-inliner-workaround/A_1.java
@@ -0,0 +1,13 @@
+public class A_1 {
+  public static class T { }
+
+  public static class Inner {
+    public static class T { }
+
+    public void foo(T t) { }
+
+    public T t = null;
+
+    public class Deeper extends T { }
+  }
+}
diff --git a/test/files/pos/t9111-inliner-workaround/Test_1.scala b/test/files/pos/t9111-inliner-workaround/Test_1.scala
new file mode 100644
index 0000000000..1a00fff833
--- /dev/null
+++ b/test/files/pos/t9111-inliner-workaround/Test_1.scala
@@ -0,0 +1,10 @@
+object Test extends App {
+  println(new A_1.Inner())
+
+  // Accessing foo or Deeper triggers the error of SI-9111.
+  // However, when not referring to those definitions, compilation should
+  // succeed, also if the inliner is enabled.
+
+  // println(i.foo(null))
+  // new i.Deeper()
+}