我看过他们在很多相同的方式使用，我很担心我将要往下走的路径设计是不可逆的，如果我不明白这更好。另外，我使用.NET。

I've seen them used in a lot of the same ways, and I am worried I'm about to go down a path in design that is irreversible if I don't understand this better. Also, I am using .NET.

推荐答案

收藏＆LT; T＆GT; 约可定制包装的IList＆LT; T＆GT; 。虽然的IList＆LT; T＆GT; 不是密封的，它不提供任何定制点。 收藏＆LT; T＆GT; 的方法都默认委托给标准的IList＆LT; T＆GT; 的方法，但可以很容易地重写做你想要什么。它也可以wireup内部事件收藏＆LT; T＆GT; ，我不相信能有一个IList来完成

Collection<T> is a customizable wrapper around IList<T>. While IList<T> is not sealed, it doesn't provide any customization points. Collection<T>'s methods are by default delegated to the standard IList<T> methods, but can be easily overridden to do what you want. It is also possible to wireup events inside a Collection<T> that I don't believe could be done with an IList.

在短，它更容易给它的事实，这可能意味着少了很多的重构后延伸。

In short, it's much easier to extend it after the fact, which could potentially mean a lot less refactoring.