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, 0 insertions, 20 deletions

diff --git a/test/pending/neg/scopes.scala b/test/pending/neg/scopes.scala
deleted file mode 100644
index fd31ff5f72..0000000000
--- a/test/pending/neg/scopes.scala
+++ /dev/null
@@ -1,20 +0,0 @@
-case class test0(x: Int, x: Float)
-
-object test1 {
-  type t = Int
-  type t = Float
-  val x: Int = 0
-  val x: Float = .0f;
-  {
-    val y: Int = 0
-    val y: Float = .0f
-    ()
-  }
-  def f1(x: Int, x: Float) = x
-  def f2(x: Int)(y: Int, y: Float) = x + y
-  val closure = (x: Int, x: Float) => x
-  List() match {
-    case x::x => x
-    case Nil => Nil
-  }
-}