Fix #1146: Fix bug of ExpandSAMs with non-apply SAM methods.

When expanding a SAM, ExpandSAMs always used the name `apply` for
the generated forwarder, instead of the name of the method which
is abstract in the SAM type. This commit fixes this issue.

2 files changed, 12 insertions, 0 deletions

diff --git a/tests/run/non-jvm-sam-non-apply.check b/tests/run/non-jvm-sam-non-apply.check
new file mode 100644
index 000000000..b8626c4cf
--- /dev/null
+++ b/tests/run/non-jvm-sam-non-apply.check
@@ -0,0 +1 @@
+4
diff --git a/tests/run/non-jvm-sam-non-apply.scala b/tests/run/non-jvm-sam-non-apply.scala
new file mode 100644
index 000000000..e3bfac928
--- /dev/null
+++ b/tests/run/non-jvm-sam-non-apply.scala
@@ -0,0 +1,11 @@
+// shouldn't result in an abstract method error when run
+abstract class NonJVMSam {
+  def foo(x: Int): Int
+}
+
+object Test {
+  def main(args: Array[String]): Unit = {
+    val f: NonJVMSam = x => x + 1
+    println(f.foo(3))
+  }
+}