Changes between Version 21 and Version 22 of Records/OverloadedRecordFields/Implementation


Ignore:
Timestamp:
Aug 1, 2013 6:00:54 PM (9 months ago)
Author:
adamgundry
Comment:

future considerations

Legend:

Unmodified
Added
Removed
Modified
  • Records/OverloadedRecordFields/Implementation

    v21 v22  
    160160 
    161161How should deprecation work for fields? Not at all? 
     162 
     163Consider error messages: can we give helpful feedback so users don't have to understand the details of the implementation? For example, unsolved `Accessor` or `Has` constraints could be given nicer messages. 
     164 
     165Consider defaulting `Accessor p` to `p = (->)`, and defaulting `Has r "f" t` constraints where there is only one datatype with a field `f` in scope.