Talk:Collections: Difference between revisions

Seconded. It's unclear what "objects" should be in a language that doesn't have any objects, but where all "collections" are polymorphic anyway, and hence can store any type (not only primitive types). And why is it necessary to have this restriction in the first place? To rule out simple C-style arrays? It's also unclear what interface a "collection" should expose (other that than one can add elements). In many languages, collections offer a generic way to unify '''access''' to some concrete container datatype, with operations like ''map'', ''fold'' (sometimes called ''reduce''), or ''filter'' (sometimes called ''select''). Is that what is meant here? If so, is only the generic interface of interest, or also concrete implementations (lists, arrays, various trees)? --[[User:DirkT|Dirk Thierbach]] 18 November 2007

: Clarified. I removed the type restriction, as well. --[[User:Short Circuit|Short Circuit]] 12:57, 21 November 2007 (MST)