Collections (was: Arrays)

Following on an earlier e-mail about refactoring Arrays... In noodling around with collections, sets, maps, arrays, I seem to have duplicated (a very small piece of) some of SPJ's work in "Bulk types with class"... from 9 years ago... In particular, Section 4 lays out the beginning steps of how to use multiparameter classes to implement a consistent set of Collections and subclasses. I know that I floated something similar a couple of weeks ago, but, based on the above, I thought that I'd float a more specific proposal: ------------ In Haskell', "collection"-style classes will be moved from the Data module and to the Collection module. Modules would be organized something like as follows: Collection .Array .Map .Set .Tree .Binary .Rose Data . ... . Int . ... Backwards compatibility can be maintained by leaving deprecated Data classes. -------- If there's no objection, I'll create a proposal ticket and flesh out the proposal more clearly. - Alson

On 3/2/06, Alson Kemp
the beginning steps of how to use multiparameter classes to implement a consistent set of Collections and subclasses.
See also this blurb from HWN: " * RFC: Class-based collections. Jean-Philippe Bernardy [25]released an rfc for his initial work on a [26]class-based collections framework. The main goal is to have something usable right now, making use of generally available haskell extensions for maximum usability/portability ratio (or rather product). 25. http://article.gmane.org/gmane.comp.lang.haskell.libraries/4291 26. http://hackage.haskell.org/trac/ghc/wiki/CollectionClassFramework " Jim
participants (2)
-
Alson Kemp
-
Jim Apple