…or can I use ICollection with no problem?
I mean, I don’t think ICollection was designed for Sorted collections because that could break an application designed for sorted or unserted ICollection objects, but I don’t know.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
…or can I use ICollection with no problem?
I mean, I don’t think ICollection was designed for Sorted collections because that could break an application designed for sorted or unserted ICollection objects, but I don’t know.
I’d say the ICollection<T> Interface is suitable for implementation by sorted collection types, because a sorted collection can be enumerated, added to, removed from, cleared and checked for its contents.
As a counter-example, the IList<T> Interface is probably not suitable, because unlike ICollection<T> it assumes that the collection is a list where the elements can be added at specific positions, which doesn’t make sense if the collection itself determines the position of each element.
The sorted collection types in the .NET Framework (the SortedList<TKey, TValue> Class, SortedDictionary<TKey, TValue> Class, and SortedSet<T> Class) all implement ICollection<T> but not IList<T>.