Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | The next batch of tests put up a little more st... | Paul Phillips | 2010-10-02 | 1 | -20/+0 |
| | | | | | | | | | | | | | | 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. | ||||
* | Sorting through the tests in pending from oldes... | Paul Phillips | 2010-10-02 | 1 | -10/+10 |
| | | | | | | | | | | | | | | | | | Sorting through the tests in pending from oldest to newest because I don't believe in having useless appendages. The verdict on the oldest fifteen tests is: 15/15 are fixed. Many were already in files under a different name. I moved a few and deleted the rest. Fun fact of the day: apparently there was a time when to call into java varargs with no arguments you might have to write something like: getClass().getMethod("getCount", Array[java.lang.Class[T] forSome { type T }]()) On this basis I retract any complaints I've ever had about anything. There is one question mark outlined in pos/testCoercionThis.scala, a file formerly called pos/moors.scala and therefore... review by moors. | ||||
* | Moving currently problematic tests to pending. | Geoffrey Washburn | 2008-08-05 | 1 | -0/+20 |
| | |||||
* | moved from pending | michelou | 2006-12-13 | 1 | -14/+0 |
| | |||||
* | added test for already defined values | michelou | 2006-12-12 | 1 | -0/+14 |