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, 35 deletions

diff --git a/test/pending/run/deprecated.scala b/test/pending/run/deprecated.scala
deleted file mode 100644
index 122e339d2f..0000000000
--- a/test/pending/run/deprecated.scala
+++ /dev/null
@@ -1,35 +0,0 @@
-object Test {
-  abstract class AbstractStuff {
-    def dostuff: Unit
-  }
-
-  [postabstract]
-  class BlueStuff extends AbstractStuff {
-    [deprecated] def dostuff = Console.println("blue")
-    def five = "five"
-  }
-
-  class LightBlueStuff extends BlueStuff {
-    [deprecated] override def dostuff = {Console.println("light blue")}
-
-    // warning: deprecated method overrides a concrete method
-    [deprecated] override def five = "light five"
-  }
-
-  // warning: not marked as postabstract
-  class RedStuff extends AbstractStuff {
-    [deprecated] def dostuff = Console.println("red")
-  }
-
-
-  def main(args: Array[String]) {
-    //  warning: BlueStuff will be abstract after deprecated methods are removed
-    val blue = new BlueStuff
-
-    //  warning: RedStuff will be abstract after deprecated methods are removed
-    val red = new RedStuff
-
-    //  warning: dostuff is deprecated
-    blue.dostuff
-  }
-}