Changes between Version 148 and Version 149 of TypeFunctionsStatus


Ignore:
Timestamp:
Aug 21, 2007 3:30:27 AM (8 years ago)
Author:
chak
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TypeFunctionsStatus

    v148 v149  
    7474 * Equational constraints in contexts.
    7575
    76 == Testsuite ==
     76== Testsuite for type family patches ==
    7777
    7878Current `validate` result:
     
    9999}}}
    100100
    101  * Class1: Ok.  (Only marked to fail in head to keep validate happy.)
    102  * Relf2: Type family BUG.
    103  * Simple5a: Changed error message for data families, BUT the new error message is cryptic and indicates a much too complicated treatment of data families.
     101 * Class1: VALID.  (Only marked to fail in head to keep validate happy.)
     102 * Relf2: VALID. Type family BUG.
     103 * Simple5a: VALID. Changed error message for data families, BUT the new error message is cryptic and indicates a much too complicated treatment of data families.
    104104 * break001: INVALID.  GHC panic instead of printing error message about ambiguous variable.
    105105 * break006: INVALID.  Seems to be the same problem as break001.
    106106 * print019: INVALID.  Seems to be the same problem as break001.
    107  * rw: Changed error message for GADTs.  Seems to be the same behaviour as in Simple5a.
     107 * rw: VALID. Changed error message for GADTs.  Seems to be the same behaviour as in Simple5a.
    108108 * tc210: INVALID (matching `forall a.a -> Int` against `Int -> Int fails).
    109109 * tc211: INVALID (tests impredicative types).
    110  * tcfail046: Changed error message, BUT the new error message has one more type synonym unfolding, which should be avoided.
    111  * tcfail071: Changed error message (has now only one of two parts).  Unsure whether the lack of the second part signals regress.
     110 * tcfail046: VALID: Changed error message, BUT the new error message has one more type synonym unfolding, which should be avoided.
     111 * tcfail071: ?? Changed error message (has now only one of two parts).  Unsure whether the lack of the second part signals regress.
     112 * tcfail102: VALID.
     113 * tcfail128: VALID. Same as tcfail046.
     114 * tcfail145: VALID. Error message got worse.
     115 * 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.
     116 * while: VALID. Works if definition of `succeed` gets a type signature `Monad m => a -> m a`.  The error seems to be due to the new GADT rules about annotations, but the error message is a bit strange; ie, need to be improved.