DData

[Dylan Thurston]

On Mon, Apr 05, 2004 at 03:53:48PM +0200, Wolfgang Jeltsch wrote:
> If I remember correctly, DData was intended to be the next-generation standard 
> set of collection modules.  So, maybe, we should just name the modules 
> Data.Map, Data.Seq, etc.  I think, it was already said that this should 
> probably be done.  A problem is Data.Set but there may be a solution for 
> this.

I think this may be controversial.  In particular, there's already
Data.Edison, which is competing, and some people feel strongly that a
class-based approach to overloading should be at least supported.

I think this might be a good case for having a 'selector' library.
Put DData under Data.DData.*, and have Data.Set (e.g.) re-export
Data.DData.Set (since that's the most complete implementation at the
moment).

Peace,
	Dylan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://www.haskell.org//pipermail/libraries/attachments/20040405/69b694e3/attachment.bin