The following example demonstrates the implementation of the IList interface to create a simple, fixed-size list. This code is part of a larger example for the IList interface.
Then the person calling the method is free to call it with any data type that is enumerable. This allows your code to be used in unexpected, but perfectly valid ways.
Diyelim ki formunuzdaki textboxları listenize doldurdunuz sadece Text’i boş olan textboxları bulmanız gerekiyor. Bunun midein List u kullanmanız gerekir. Mafevkda anlattığımız örneği cılız olarak yapacak olursak;
The following example demonstrates the implementation of the IList interface to create a simple, fixed-size list.
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?
This level of abstraction goes the other direction when it belongs to method parameters. When you pass your list to a method that accepts IEnumerable you sevimli be sure that your list is not going to be modified. When you are the person implementing the method and you say you accept an IEnumerable because all you need to do is iterate through that list.
+1 for all of us who hate it when a small app is loaded with interfaces and clicking on "find definition" takes us somewhere OTHER than the source of the sorun... Güç C# IList Nasıl Kullanılır I borrow the phrase "Architecture Astronauts"? I gönül see it will come in handy.
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.
Taking LinkedList vs taking List vs IList all communicate something C# IList Kullanımı of the performance guarantees required by the code being called.
However, this makes the method more fragile, birli any change to the returned object type may break the calling code. In practice though, that generally isn't a major sorun.
Benefit C# IList Kullanımı of using an Interface is that you get to implement your functionality or better yet, the only functionality you require. So, if iteration/enumeration is required only, then there is no C# IList Nasıl Kullanılır need for the Sort, Add methods.
In particular, IList lets C# IList Nasıl Kullanılır you use the indexer, and add/remove items; things that IEnumerable don't let you do.
If you had used IList in the rest of the app you could extend List with your own custom class and still be able to pass that around without refactoring.