Kısaca IEnumerable dokumasında filtreleme çalışmalemleri memory bile bünyelırken, IQueryable da veritabanından düver filtrelenmiş verileri elde ederiz.
IList is an interface so you birey inherit another class and still implement IList while inheriting List prevents you to do so.
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 bey well? So maybe IList to IList?
You yaşama have an instance of an interface, but you need to C# IList Nerelerde Kullanılıyor initialize it with a class that implements that interface such kakım:
I thought I'd never need to change from a List but had to later change to use a custom list library for the extra functionality it provided. Because C# IList Neden Kullanmalıyız I'd only returned an IList none of the people that used the library had to change their code.
Ask those people what they'd like the methods to return. Your question is fundamentally C# IList Kullanımı "how do I know what software to write?" You know by getting to know what problems your customer özgü to solve, and writing C# IList Nerelerde Kullanılıyor code that solves their problems.
For example, let's say you have a Person class and a Group class. A Group instance saf many C# IList Neden Kullanmalıyız people, so a List here would make sense. When I declare the list object in Group I will use an IList and instantiate it bey a List.
Taking LinkedList vs taking List vs IList all communicate something of the performance guarantees required by the code being called.
In this case you could pass in any class which implements the IList interface. If you used List instead, only a List instance could be passed in.
And, if you used a generic implementation, you would only be able to use a method that works for any object only with objects of a specific type.
Have children's car seats not been proven to be more effective than seat belts alone for kids older than 24 months?