Changes between Version 156 and Version 157 of TypeFunctionsStatus

Timestamp:

08/26/07 21:21:06 (6 years ago)

Author:

chak

Comment:

--

TypeFunctionsStatus

@@ -85 +85 @@
    tc210(normal)
    tc211(normal)
-   tcfail046(normal)
    tcfail065(normal)
    tcfail068(normal)
@@ -91 +90 @@
    tcfail102(normal)
    tcfail103(normal)
-   tcfail128(normal)
    tcfail179(normal)
 }}}
@@ -104 +102 @@
  * tc210: INVALID (matching `forall a.a -> Int` against `Int -> Int fails).
  * tc211: INVALID (tests impredicative types).
- * tcfail046: VALID.  Changed error message, BUT the new error message has one more type synonym unfolding, which should be avoided.
+ * ~~tcfail046~~: VALID.  Changed error message, BUT the new error message has one more type synonym unfolding, which should be avoided.
  * tcfail065: VALID.  Cosmetic difference, as tidy names are assigned in different order.
  * tcfail068: ?? Reports two errors less (probably due to different recovery points)
@@ -111 +109 @@
  * tcfail102: VALID.
  * tcfail103: VALID.  Error message is actually better!
- * tcfail128: VALID. Same as tcfail046.
+ * ~~tcfail128~~: VALID. Same as tcfail046.
  * ~~tcfail145~~: VALID. Error message got worse.
  * ~~tcfail153~~: VALID. Related to Simple5a in that a match against a rigid type variable gets reported as an equality context that could not be deduced.
@@ -120 +118 @@
  0. ~~Panic in case of ambiguous type variables (break001, break006, and print019).~~
  0. Problem instantiating rank-2/impredicative types (tc210 & tc211).
-
-----
-Local:
-{{{
-Unexpected passes:
-   Class1(normal)
-   GADT2(normal)
-
-Unexpected failures:
-   Refl2(normal)
-   tc210(normal)
-   tc211(normal)
-   tcfail046(normal)
-   tcfail065(normal)
-   tcfail068(normal)
-   tcfail076(normal)
-   tcfail102(normal)
-   tcfail103(normal)
-   tcfail128(normal)
-   tcfail179(normal)
-   while(normal)
 }}}