Talk:Collections: Difference between revisions
No edit summary |
(Please clarify task) |
||
| Line 1: | Line 1: | ||
"Collections", as a task, is far from being clearly defined. Can someone add a brief description or a list of task requirements? --[[User:Shock|Shock]] 20:24, 24 January 2007 (EST) |
"Collections", as a task, is far from being clearly defined. Can someone add a brief description or a list of task requirements? --[[User:Shock|Shock]] 20:24, 24 January 2007 (EST) |
||
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 |
|||
Revision as of 15:42, 21 November 2007
"Collections", as a task, is far from being clearly defined. Can someone add a brief description or a list of task requirements? --Shock 20:24, 24 January 2007 (EST)
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)? --Dirk Thierbach 18 November 2007