Changes between Version 68 and Version 69 of TypeFunctionsStatus

Timestamp:

08/26/06 16:19:35 (7 years ago)

Author:

chak

Comment:

--

TypeFunctionsStatus

@@ -10 +10 @@
 Todo (low-level):
  * ''Imported'' data family tycon cannot be extended (GHC claims its not in scope in the data instance declaration) - cf. `MapPS.hs`.
- * Probably remove the `iso` flag.
+ * Should family declarations be optional with ATs, too?  (See comment at patch making kinds optional at toplevel declarations.)
 
 Todo (high-level):
- 1. Make the kind specification optional in family declarations.  (How to do the representation in the data/newtype case is not entirely clear, as we use the presence of the kind signature at the moment to identify family declarations.)
- 2. Parse and rename equality constraints in signatures.
- 3. Defaults for associated type synonyms.  (Having both a kind signature and vanilla synonym is problematic as in `RnNames.getLocalDeclBinders` its hard to see that not both of them are defining declarations, which leads to a multiple declarations error.  Defaults are quite different from vanilla synonyms anyway, as they usually have tyvars on their rhs that do not occur on the lhs.)
- 4. Import/export lists:
+ 1. Parse and rename equality constraints in signatures.
+ 2. Defaults for associated type synonyms.  (Having both a kind signature and vanilla synonym is problematic as in `RnNames.getLocalDeclBinders` its hard to see that not both of them are defining declarations, which leads to a multiple declarations error.  Defaults are quite different from vanilla synonyms anyway, as they usually have tyvars on their rhs that do not occur on the lhs.)
+ 3. Import/export lists:
    * We need to be able to write something like `GMapKey(GMap,empty)`.
    * Export and import of data constructors declarated in `data instance`s.  We should be able to use the same syntax for the entity specs as for closed data types, but the meaning is somewhat different.