views:

1536

answers:

6

I saw this reply from Jon on Initialize generic object with unknown type

If you want a single collection to contain multiple unrelated types of values, however, you will have to use List<object>

I'm not comparing ArrayList vs List<>, but ArrayList vs List<object>, as both will be exposing item of type "object". What would be the benefit of using either one in this case?

EDIT: It's no concern for type safety here, since both class is exposing object as it's item. One still need to cast from object to the desired type. I'm more interested in anything other than type safety

EDIT: Thanks Marc Gravell and Sean for the answer. Sorry, I can only pick 1 as answer, so I'll up vote both.

A: 

List<> is a typesafe version of ArrayList. It will guarantee that you will get the same object type in the collection.

Funky81
Obviously I'm not referring to type safety here
faulty
+4  A: 

Yes, besides being typesafe, generic collections might be actually faster.

From the MSDN (http://msdn.microsoft.com/en-us/library/system.collections.generic.aspx)

The System.Collections.Generic namespace contains interfaces and classes that define generic collections, which allow users to create strongly typed collections that provide better type safety and performance than non-generic strongly typed collections.

DrJokepu
+10  A: 

One big benefit to using List<object> is that these days most code is written to use the generic classes/interfaces. I suspect that these days most people would write a method that takes a IList<object> instead of an IList. Since ArrayList doesn't implement IList<object> you wouldn't be able to use an array list in these scenarios.

I tend to think of the non-generic classes/interfaces as legacy code and avoid them whenever possible.

Sean
That was an angle I didn't think about, good catch.
Lasse V. Karlsen
+8  A: 

In this case, ArrayList vs. List<Object> then you won't notice any differences in speed. There might be some differences in the actual methods available on each of these, particular in .NET 3.5 and counting extension methods, but that has more to do with ArrayList being somewhat deprecated than anything else.

Lasse V. Karlsen
+5  A: 

You'll be able to use the LINQ extension methods directly with List<object>, but not with ArrayList, unless you inject a Cast<object>() / OfType<object> (thanks to IEnumerable<object> vs IEnumerable). That's worth quite a bit, even if you don't need type safety etc.

The speed will be about the same; structs will still be boxed, etc - so there isn't much else to tell them apart. Except that I tend to see ArrayList as "oops, somebody is writing legacy code again..." ;-p

Marc Gravell
+1  A: 

Do some benchmarking and you will know what performs best. I guestimate that the difference is very small.

tuinstoel
actually im not sure the question is about performance but that is a good point. my guess is arraylist perf would be worse due to additional boxing, unboxing.
Anonymous Type