Changes between Version 31 and Version 32 of Records


Ignore:
Timestamp:
Jan 8, 2012 1:11:40 AM (4 years ago)
Author:
GregWeber
Comment:

remove redundant

Legend:

Unmodified
Added
Removed
Modified
  • Records

    v31 v32  
    5555=== Type directed name resolution ===
    5656
    57 The discussion has many similarities with the original Type directed name resolution proposal: the question seems to be largely about nailing down a concrete implementation; see below and [http://hackage.haskell.org/trac/haskell-prime/wiki/TypeDirectedNameResolution TDNR]. The original TDNR proposal had Overloading in mind, but Namespacing ends up having similarities. -- Greg Weber
     57The discussion has many similarities with the original Type directed name resolution proposal: the question seems to be largely about nailing down a concrete implementation. The original TDNR proposal had Overloading in mind, but Namespacing ends up having similarities. -- Greg Weber
    5858
    5959All of the name-space mechanisms require some level of user-supplied disambiguation: if there are two fields `a` in scope, you must use a qualified name to disambiguate them.  What is tantalising about this is that the ''type'' of the argument immediately specifies which one you mean. There is really no ambiguity at all, so it is frustrating to have to type qualified names to redundantly specify that information.  Object-oriented languages take for granted this form of type-directed disambiguation.