Changes between Version 5 and Version 6 of CollectionClassFramework


Ignore:
Timestamp:
Jan 29, 2006 1:24:32 PM (9 years ago)
Author:
jpbernardy
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CollectionClassFramework

    v5 v6  
    33This page describes a proposal for a class framework for collection types. Related ticket: #666 
    44 
    5 Please give me feedback by either mailing me (jeanphilippe.bernardy at gmail.com)  
    6 or edit this page; or issue tickets (see CollectionLibraries); or any other means. 
    7 I'm mainly interested in concrete examples where the framework would fall short to meet your needs. 
    8  
    9 == Goals and Non-Goals == 
     5== Goals, Non-Goals and Working Hypotheses == 
    106 
    117  * Focus on practical usage. No design in the abstract; what's proposed here shall be usable, and used. 
     
    1814    Some of them are just best left in the modules to be accessed qualified. 
    1915 
    20 == Working hypotheses == 
    21  
    2216 * The classes are "implementation-based" (in opposition to the Edison idea). 
    2317   1. It seemed like a bad idea to do the same thing as something that already existed. 
    24    2. Collections are about performance anyway (otherwise everyone would use standard linked-lists). 
     18   2. Collections are (mostly) about performance anyway (otherwise everyone would use standard linked-lists). 
    2519   3. The type give information about the programmer's expected behaviour of the collection.  
    2620 * This deliberaty uses many symbols already in the prelude. The intent is that the user hides whatever clashes from Prelude, however it's also possible to import this module qualified. 
     
    2923 * Most names of classes are only tentative and should be all reconsidered. Good ideas welcome. 
    3024 
     25 
    3126== TODO == 
    3227 
    33  * Quite some functions are missing, they are ommited for the sake of brievety, 
     28 * Quite some functions are missing, they are omitted for the sake of brievety, 
    3429   until a consensus is reached on the main issues. 
    3530   Most of the time they should be trival to add though (eg. partition) 
    3631 * write instances for the new Seq type, following List.[] 
    3732 * See how Foldable/Travesable/Applicable fit this scheme.  
    38  
    39 == Code == 
    40  
    41 attachment:Coll.hs