Changes between Version 11 and Version 12 of CollectionClassFramework


Ignore:
Timestamp:
Mar 2, 2006 11:25:15 PM (10 years ago)
Author:
guest
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CollectionClassFramework

    v11 v12  
    99
    1010  * Focus on practical usage. No design in the abstract; what's proposed here shall be usable, and used.
     11  * Provide a clean separation between Collection and Data classes.
    1112  * Reduce the amount of explicit module-qualification that is currently required for collection types usage.
    1213  * Allow algorithms to be parameterized over collection types.
     
    1415  * No attempt to fit updatable/state-monad-based collections.
    1516    It looked like a bad idea to mix both updatable/non-updatable collections in a single classes framework.
     17    However, when updatable/state-monad-based collections are added, they should adopt much of the look-n-feel so as to avoid the IArray/MArray different-name-for-same-functions problem.
    1618  * No attempt to fit 100% of the existing functions into classes.
    1719    Some of them are just best left in the modules to be accessed qualified.
     
    2628 * Most names of classes are only tentative and should be all reconsidered. Good ideas welcome.
    2729
     30== References ==
     31 * SPJ's Bulk Types with Sass : http://research.microsoft.com/%7Esimonpj/Papers/collections.ps.gz
     32 * The Edison implementation of Okasaki's Functional Data Structures : http://www.eecs.tufts.edu/~rdocki01/edison.html;
     33 * Java's implementation : http://java.sun.com/j2se/1.5.0/docs/api/java/util/package-summary.html
     34 * C++ STL: http://www.cppreference.com/cppstl.html
     35
    2836== Haddock ==
    2937