Changes between Version 162 and Version 163 of TypeFunctionsStatus


Ignore:
Timestamp:
Aug 27, 2007 10:57:39 AM (8 years ago)
Author:
chak
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TypeFunctionsStatus

    v162 v163  
    8686Unexpected failures:
    8787   Refl2(normal)
    88    tc211(normal)
    8988   tcfail065(normal)
    9089   tcfail068(normal)
     
    105104 * ~~rw~~: VALID. Changed error message for GADTs.  Seems to be the same behaviour as in Simple5a.
    106105 * ~~tc210~~: INVALID (matching `forall a.a -> Int` against `Int -> Int fails).
    107  * tc211: INVALID (tests impredicative types).
     106 * ~~tc211~~: INVALID (tests impredicative types).
    108107 * ~~tcfail046~~: VALID.  Changed error message, BUT the new error message has one more type synonym unfolding, which should be avoided.
    109108 * tcfail065: VALID.  Cosmetic difference, as tidy names are assigned in different order.
     
    118117 * tcfail179: VALID.  If anything, the error message improved.
    119118 * 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.
    120 
    121 Summary of ''critical'' problems:
    122  0. ~~Panic in case of ambiguous type variables (break001, break006, and print019).~~
    123  0. Problem instantiatiating impredicative types (tc211).