Changes between Version 25 and Version 26 of Records/NameSpacing


Ignore:
Timestamp:
Jan 11, 2012 10:08:06 AM (4 years ago)
Author:
GregWeber
Comment:

remove emphasis

Legend:

Unmodified
Added
Removed
Modified
  • Records/NameSpacing

    v25 v26  
    102102=== Increased need for type annotation ===
    103103
    104 This is the only real downside of *this* proposal (most downsides discussed here are inherent to any records proposal). The Frege author says:
     104This is the only real downside of this proposal - most downsides discussed here are inherent to any records proposal. The Frege author says:
    105105
    106106I estimate that in 2/3 of all cases one does not need to write `T.e x` in sparsely type annotated code, despite the fact that the frege type checker has a left to right bias and does not yet attempt to find the type of `x` in the code that "follows" the `x.e` construct (after let unrolling etc.) I think one could do better and guarantee that, if the type of `x` is inferrable at all, then so will be `x.e` (Still, it must be more than just a type variable.)
     
    160160== Compatibility with existing records ==
    161161
    162 The new record system is enabled with `-XNAMESPACEDATA`.
     162The new record system could be enabled with `-XNAMESPACEDATA`.
    163163
    164164* Should new modules be infectious? That is, if I turn the extension on for my module and export a record, does a user that wants to import the record also have to use the extension?