System.Collections.Queue vs. System.Collections.Generics.Queue

  • Thread starter Thread starter Helium
  • Start date Start date
H

Helium

Is there any need for "System.Collections.Queue" any more? OK, .Net
made the mistake to start without generics, but that is fixed now.

Languages without support for generics could use
"System.Collections.Generics.Queue<Object>" instead of
"System.Collections.Queue". So everytime those languages use a
generic, they just use them with <object>.

I don't think having two different sets of collections is a good idea.
 
Back
Top