Changes between Version 18 and Version 19 of Records/NameSpacing
- Timestamp:
- 01/09/12 00:25:26 (18 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Records/NameSpacing
v18 v19 48 48 === Details on the dot === 49 49 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.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. 51 51 52 52 Given the dot's expanded use here, plus its common use in custom operators, it is possible to end up with dot-heavy code. … … 187 187 == Partial application == 188 188 189 see [ wiki:TypeDirectedNameResolution TDNR] syntax discusion.189 see [/wiki/TypeDirectedNameResolution TDNR] syntax discusion. 190 190 `.a r == r.a` 191 191 … … 218 218 219 219 Is 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 nicer220 Note 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 221 221 222 222
