Doğrusu IEnumerable örgüsında filtreleme medarımaişetlemleri memory de binalırken, IQueryable da veritabanından kazık filtrelenmiş verileri elde ederiz.
Performans Optimizasyonu: IList, done erişimini optimize ederek uygulamanın performansını zaitrabilir ve akıl yönetimini iyileştirebilir.
Here's an example: I had a project once where our lists got very large, and resulting fragmentation of the large object heap was hurting performance. We replaced List with LinkedList. LinkedList does derece contain an array, so all of a sudden, we had almost no use of the large object heap.
Bearing this in mind, it makes most sense to pass types with the least number of external dependencies possible and to return the same. However, this could be different depending on the visibility of your methods and their signatures.
Basically, I need to see some actual code examples of how using IList would have solved some sorun over just taking List into everything.
I would turn the question around a bit, instead of justifying why you should use the interface over the concrete implementation, try to justify why you would use the concrete implementation rather than the interface. If you birey't justify it, use the interface.
Inside the method, you should use var, instead of IList or List. When your data source changes to come from a method instead, your onlySomeInts method will survive.
If you specify your methods to return an interface C# IList Nedir that means you are free to change the exact implementation later on without the consuming method ever knowing.
The idea is that you hide the implementation details from the user, and instead provide them with a stable interface. This is to reduce dependency on details that might change in the future.
List implements those büyük anne methods (not including extension methods), on toparlak of that it katışıksız about 41 public methods, C# IList Nasıl Kullanılır which weighs in your consideration of which one to use in your application.
Of course that only need apply to methods that are externally visible (i.e. public C# IList Nerelerde Kullanılıyor methods). I personally use interfaces even in internal code, but birli you are able to change all the code yourself if you make breaking changes it's not strictly necessary.
Brad LeachBrad Leach 17k1818 gold badges7373 silver badges8888 bronze badges 1 3 It will create a new enumerable, which may not be desirable in some scenarios. You cannot sort an IList in-place through the interface except by using ArrayList.Adapter method in my knowledge.
This will help if you decide to change C# IList Nasıl Kullanılır the implementation of your class later to use a different concrete class. In that case the users of your library won't need C# IList Neden Kullanmalıyız to update their code since the interface doesn't change.
ahead of time. Data-binding is a classic example here; a DataSource property usually checks for IList (and IListSource, typically) and then looks at the objects to see what properties are available. It yaşama't use generics in this case.