I'm afraid I agree with brother Aristotle. I don't see a need for a collection class, given the power of arrays and hashes as they already are. Collection classes are generally useful in languages where arrays are limited in what they can contain, or the language doesn't support native array operations (like C, C++, or Java).
The operations you listed are already embodied in push, pop, shift, and unshift, not to mention splice as the ultimate way to slice-and-dice an array. As for creating one from another, simple assignment or slice assignment will do that too.
As for contained objects, it's true that arrays only contain scalars, but since a reference to anything fits in a scalar, that's not much of a limitation. And with Perl 6's hyper-operators, you can refer to all these much more succinctly.
Are you contemplating operations above and beyond the current array operations? Maybe you could enumerate them or give some examples.
In reply to Re: What do you like in a Collection class?
by VSarkiss
in thread What do you like in a Collection class?
by dragonchild
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |