As you might know, I've been working on a class-based framework API to accomodate existing collection types, which I intend to be used in place of the concrete modules APIs. It can be found here: http://hackage.haskell.org/trac/ghc/wiki/CollectionClassFramework By all means, I'd be interested to have your feedback on my design. I don't mean that there can exist only one, but I guess we can benefit from each other's ideas. Cheers, JP. On 2/21/06, Malcolm Wallace <Malcolm.Wallace@cs.york.ac.uk> wrote:
Robert Dockins <robdockins@fastmail.fm> wrote:
On Feb 20, 2006, at 5:19 PM, ajb@spamcop.net wrote:
Data.Set, Data.Map, Data.Hash and the various Array interfaces are all inconsistent in subtle ways, so whatever you do, do not take them as the ideal to which Edison should aspire.
This is all true. The main advantage that the current Data.* APIs have is that people use them ;-)
And AFAIK the only reason people use them is because they are widely distributed, not because they are a perfect design. I certainly have reservations about the Data.* APIs, such as the left bias and so on, and personally preferred the older Data.FiniteMap API.
Regards, Malcolm _______________________________________________ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell