Changes between Version 35 and Version 36 of Records/OverloadedRecordFields/Implementation


Ignore:
Timestamp:
Aug 12, 2013 10:50:54 AM (2 years ago)
Author:
adamgundry
Comment:

implemented warning for qualified fields

Legend:

Unmodified
Added
Removed
Modified
  • Records/OverloadedRecordFields/Implementation

    v35 v36  
    219219Of course, it is fine to use a qualified name in a record update.
    220220
     221I've implemented the first option, adding a new warning `-fwarn-qualified-overloaded-record-fields` which is on by default.
     222
     223
    221224== Outstanding bugs ==
    222225
     
    249252* Sort out GADT record updates.
    250253* Sort out data families with duplicated fields.
    251 * Sort out qualified names.
    252254* Improve error messages from typechecker:
    253255  * Unsolved `Accessor p f` where `p` is something silly
     
    257259* Where should automatic instances be generated for GHCi?
    258260* How should deprecation work for fields? Not at all?
     261* Document the extension, including new warnings.