I know there özgü been a lot of posts on this but it still confuses me why should you pass in an interface like IList and return an interface like IList back instead of the concrete list.
Arec BarrwinArec Barrwin 61.8k99 gold badges3030 silver badges2525 bronze badges 14 71 I have to disagree with your sardonic answer. I don't totally disagree with the sentiment of over-architecture being a real problem. However I think that especially in the case of collections that interfaces really shine.
Also, it casts IList to IList which katışıksız the potential to be dangerous. In most cases that I have seen, List which implements IList is used behind the scenes to implement IList, but this is not guaranteed and dirilik lead to brittle code.
Then click on the bulb symbol or place the cursor on the IList and press Strg + "." You will become several implementations offered, like:
Bağlı listeler, devimsel muta gestaltlarıdır. Bu sayede araya eleman ekleme, silme kadar işlemler henüz emeksiz bir şekilde örgülabilir. Bu alfabemızda destelı listelerin detaylarından bahsedeceğiz.
List is a specific implementation of IList, which is a container that dirilik be addressed the same way birli a linear array T[] using an integer index. When you specify IList kakım the type of the method's argument, you only specify that you need certain capabilities of the container. For example, the interface specification does not enforce a specific data structure to be used.
Object yaşama be a T too. Doing this will save you headache if you decide to use a Stack or some other veri 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.
If you started with a concrete type and you decided to change to another one, even if it uses the same interface, you're going to C# IList Nasıl Kullanılır break someone else's code unless you started off with an interface or abstract base type. Share Improve this answer Follow
Taking LinkedList vs taking List vs IList all communicate something of the performance guarantees required by the code being called.
IList.IsFixedSize bileğerinin mıhlı bir boyuta mevla olup olmadığını IList tamlayan bir fehamet kırmızıır.
In this case you could pass in any class which implements the IList interface. If you used List instead, only C# IList Nasıl Kullanılır a List instance could be passed in.
In particular, IList lets you use the indexer, and add/remove items; things C# IList Neden Kullanmalıyız that IEnumerable don't let you do.
additional advantage is that your code is safe from any changes to concrete class birli you are subscribing to only few of the methods of concrete class and those are C# IList Nasıl Kullanılır the ones that are going to be there bey long kakım the concrete class inherits from the C# IList Neden Kullanmalıyız interface you are using.