Bir İnceleme C# IList Neden Kullanmalıyız

Bir İnceleme C# IList Neden Kullanmalıyız

Blog Article

I toyed with writing an extension method, also with inheriting from IList and implementing my own Sort() method as well as casting to a List but none of these seemed overly elegant.

Lütfen adidaki kutuya şikayetinizin bilgilerinı yazın. Şikayetinizi değerlendirildikten sonrasında size fen vereceğiz.

Important Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.

Eric LippertEric Lippert 656k182182 gold badges1.3k1.3k silver badges2.1k2.1k bronze badges 14 12 How do you know what the caller needs though. For instance I was switching one of my return types to a IList then I well I am probably just going to enumerate over them anyways lets just return an IEnumberable.

ToList first? How about returning it? I don't understand what you mean by "method will survive" when using vars? I know it will be a bit more work but won't you just have to change that to the new type kakım well? So maybe IList to IList?

The Liskov Substitution Principle (simplified) states that a derived type should be able to be used in place of a base C# IList Neden Kullanmalıyız type, with no additional preconditions or postconditions.

Object birey be a T too. Doing this will save you headache if you decide to use a Stack or some other data structure further down the road. If all you need to do in the function is foreach through it, IEnumerable is really all you should be asking for.

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.

For example, let's say you have a Person class and a Group class. A Group instance özgü many people, so a List here would make sense. When I declare the list object in Group I will use an IList and instantiate it as a List.

It really comes down to the kind of functionality you need. I'd suggest using the List class in most cases. IList is best for C# IList Neden Kullanmalıyız when you need to make a custom array that could have some very specific rules that you'd like to encapsulate within a collection so you don't repeat yourself, but still want .Kemiksiz to recognize it birli a list.

kemiller2002kemiller2002 115k2828 gold badges198198 silver badges253253 bronze badges Add a comment  

Coming soon: Throughout 2024 C# IList Neden Kullanmalıyız we will be phasing out GitHub Issues bey the feedback mechanism for content and replacing it with a new feedback system. For more information see: C# IList Nasıl Kullanılır .

If you use a concrete implementation of list, another implementation of the same list will hamiş be supported by your code.

The other general reason for using C# IList Nedir interfaces is to expose the minimum amount of knowledge necessary to the user of an object. Consider the (contrived) case where I have a veri object that implements IList.