Why isn’t ArrayList marked [Obsolete]?

I think it should be considered effectively obsolete for new code, but there’s no compelling reason to mark it obsolete and create warnings in all code which was written before 2.0 was released.

In my experience, most of the types and members which have been marked obsolete by Microsoft are actively dangerous in some respect, and should really be fixed if you still have a codebase using them. While using ArrayList is painful and (at least theoretically) prone to discovering type-related bugs at execution time rather than compile time, the type does its job well enough… often there’s really no compelling reason to change existing code. It’s the kind of change I’d generally consider when I already happened to be working on an area of code which was using ArrayList, rather than actively seeking out every usage of it.

Leave a Comment