Changes between Version 30 and Version 31 of Records/OverloadedRecordFields/Plan


Ignore:
Timestamp:
Aug 12, 2013 8:29:02 AM (8 months ago)
Author:
adamgundry
Comment:

avoid ambiguous "monomorphic"

Legend:

Unmodified
Added
Removed
Modified
  • Records/OverloadedRecordFields/Plan

    v30 v31  
    127127 * records may include higher-rank components. 
    128128 
    129 These problems have already been [wiki:Records/OverloadedRecordFields#Recordupdates described in some detail]. In the interests of doing something, even if imperfect, the Haskell 98 record update syntax will support only monomorphic update. For overloaded fields to be updated, a type signature may be required in order to specify the type being updated. For example, 
     129These problems have already been [wiki:Records/OverloadedRecordFields#Recordupdates described in some detail]. In the interests of doing something, even if imperfect, the traditional record update syntax will support only non-overloaded update (that is, update of a unique known record type). Where overloading mean that the fields alone do not determine the type being updated, a type signature may be required. For example, 
    130130{{{ 
    131131e { x = t }