The next batch of tests put up a little more st...

The next batch of tests put up a little more struggle, but only a
little. See test/pending/pos/unappgadteval.scala (the changes for which
were in the previous commit) for an example of a test which might be on
to something. Any idea what it would take to get it working?

  // the key lines
  case i @ Suc()          => { (y: Int) => y + 1 }      // a = Int => Int
  case f @ Lam[b,c](x, e) => { (y: b) => eval(e, env.extend(x, y)) }  // a = b=>c

No review.

1 files changed, 17 insertions, 0 deletions

diff --git a/test/files/run/bug874.scala b/test/files/run/bug874.scala
new file mode 100644
index 0000000000..d83014651b
--- /dev/null
+++ b/test/files/run/bug874.scala
@@ -0,0 +1,17 @@
+object Test {
+  abstract class Base {
+    val U: {
+      def apply[A](x1: A)(x2: Int): Any
+    }
+    U("xyz")(2)
+  }
+  class Mix extends Base {
+    case class U[A](x1: A)(x2: Int) {
+      Console.println("U created with "+x1+" and "+x2)
+    }
+  }
+  def main(args : Array[String]) : Unit = {
+    val obvious: Base = new Mix;
+    obvious.U("abc")(1)
+  }
+}