Changes between Version 78 and Version 79 of TypeFunctionsStatus


Ignore:
Timestamp:
Sep 5, 2006 9:00:03 PM (9 years ago)
Author:
chak
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TypeFunctionsStatus

    v78 v79  
    44
    55'''Current:'''
    6  * Next: Check for overlapping instances and fix importing/exporting of families and their instances.
     6 * Next: (1) Last bist of import/export functionality; (2) check for overlapping instances.
    77
    88== Parsing and Renaming ==
    99
    1010Todo (low-level):
    11  * ''Imported'' data family tycon cannot be extended (GHC claims its not in scope in the data instance declaration) - cf. `MapPS.hs`.
    12  * Should family declarations be optional with ATs, too?  (See comment at patch making kinds optional at toplevel declarations.)
     11  * Should family declarations be optional with ATs, too?  (See comment at patch making kinds optional at toplevel declarations.)
    1312
    1413Todo (high-level):
     
    2726
    2827Todo (low-level):
    29  * data/newtype instances may not overlap.  (Such definitions would always be non-confluent.)  We might be able to get away with a lazy check at every place where a value of family type is constructed (i.e., occurences of the datacon wrapper).  Such a value may never be an inhabitant of more than one instance declaration.
     28 * data/newtype instances may not overlap.  (Such definitions would always be non-confluent.)  We might be able to get away with a lazy check at every place where a value of family type is constructed (i.e., occurences of the datacon wrapper).  Such a value may never be an inhabitant of more than one instance declaration.  No, we won't get away with this...
    3029 * RHS of a `type instance` must be a tau type.
    3130 * Check that patterns of type indexes don't contain type functions.
     
    4645
    4746Todo (low-level):
    48  * When a family type is exported/imported, all its instances need to be implicitly imported/exported, just as with classes.
     47 * In export and import lists, it must be possible to mention AT names as sub-components of a class.
     48 * `data instances` and `newtype instances` need to be implicitly exported as are class instances.
    4949 * Derivings on an associated data type ''declaration'' need to be inherited by all definitions of that data type in instances.
    5050