Aren't data structures what you learn in school, so when you hit the real world you're ready to implement/optimize what someone else has already implemented/optimized for you? I'm willing to pull out the old textbooks, RTFM and give a whirl at some optimizations. Unfortunately if anyone asks me to prove their speed, I'm SOL.
Besides, I think a poor (or nonexistent) collections API is key to a good adoptation of any language. That and arcane syntax:
template<typename T, size_t N>
inline void foreach(T (&array)[N], void (*f)(T) )
{
for(int i=0; i < N; i++)
{
(*f)(array[i]);
}
}
BTW I think java.util.collections is my most imported package in Java. I really do think scala needs a great collections library. The API is great (from what I've used so far), so if the speed improves It'd be an easy sell.
On Tue, Jul 29, 2008 at 8:07 PM, David MacIver
<david.maciver@...> wrote:
On Wed, Jul 30, 2008 at 1:03 AM, David Pollak
<
feeder.of.the.bears@...> wrote:
> Gee David... the is so "academic"... I mean you're testing things and all.
> :-) :-) :-)
structures. Arrays should be good enough for anyone. :-)
