Design pattern for internal node of a generic collection

Hot Topic

How do I add windows form controls without setting the positioning or location
Foreach loop
How to use TypeConverter
DataReader Table and Column names
When does P/Invoke free a DLL from memory again ?
Exception thrown in delegate causing problems
Typing in Visual Studio 2005 Text Editor is extremely slow
Using C# Express!
About solution folder - A bug or not?
CRectTrack

Visual C#

Custom Attributes
Components parameters
Crystal Reports Report Document
Empty C# application use almost 20mb memory
Help please
creating DLL's
How to list driver in combobox?
Blocking ALT+CTRL+DEL in your application!
sql connection string
CallBack from a WIN 32 C++ dll

Design pattern for internal node of a generic collection

I am currently design a complicated generic collection with .Net 2.0. Basically I have the following design:


class MyCollection<T> : ICollection<T>
{
    private class MyNode<T>
    {
       // snipped
    }
}
 


When compiled, this code generates a warning saying that T is confusing because used both for MyCollection and MyNode. In practice, the T will be same in both classes. What would you suggest as the correct design pattern for such a situation

Thanks in advance,
Joannes

Answer this question

Design pattern for internal node of a generic collection

  • doug2008

    Simply omit type argument from MyNode.

    Since it's nested type of MyCollection<T> it already know type T.

    Read 20.1.12 Nested Types in generic classes for a reference.

     

     
  • Design pattern for internal node of a generic collection
Answer this question