Changes between Version 18 and Version 19 of Records/NameSpacing


Ignore:
Timestamp:
Jan 9, 2012 8:25:26 AM (3 years ago)
Author:
GregWeber
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Records/NameSpacing

    v18 v19  
    4848=== Details on the dot === 
    4949 
    50 This proposal requires the current Haskell function composition dot operator to have spaces on both sides. No spaces around the dot are reserved for name-spacing: this use and the current module namespace use. No space to the right would be partial application (see [wiki:TypeDirectedNameResolution TDNR]. The dot operator should bind as tightly as possible. 
     50This proposal requires the current Haskell function composition dot operator to have spaces on both sides. No spaces around the dot are reserved for name-spacing: this use and the current module namespace use. No space to the right would be partial application (see [wiki:TypeDirectedNameResolution](TDNR). The dot operator should bind as tightly as possible. 
    5151 
    5252Given the dot's expanded use here, plus its common use in custom operators, it is possible to end up with dot-heavy code. 
     
    187187== Partial application == 
    188188 
    189 see [wiki:TypeDirectedNameResolution TDNR] syntax discusion. 
     189see [/wiki/TypeDirectedNameResolution TDNR] syntax discusion. 
    190190`.a r == r.a` 
    191191 
     
    218218 
    219219Is there are more convenient syntax for this? `b <.a` 
    220 Note that a move to a different operator for function composition would make things much clearer: `b <~ .a`, where the unicode dot might be even nicer 
     220Note that a move to a different operator for function composition (see brief discussion of the dot operator above) would make things much clearer: `b <~ .a`, where the unicode dot might be even nicer 
    221221 
    222222