Greatest Kılavuzu C# IList Kullanımı için

Greatest Kılavuzu C# IList Kullanımı için

Blog Article

It's always best to use the lowest base type possible. This gives the implementer of your interface, or consumer of your method, the opportunity to use whatever they like behind the scenes.

IList is an interface so you can inherit another class and still implement IList while inheriting List prevents you to do so.

Also, it casts IList to IList which saf 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 hamiş guaranteed and kişi lead to brittle code.

Your functions above only care about being able to iterate over a list. Ideally they shouldn't need to know who implements that list or how they implement it.

Ayrıca fevkda anlattığımız IndexOf metodunu Asıl liste üzerinden ast listelerdeki elemanlar ciğerin kullanamazsınız. Esas liste üzerinden alt listelerin index sırasını bulabilirsiniz.

Buraya dikkat etmenizi isterim. Liste tipine textbox dedik ve listeye textbox eklerken bile direk nesne adını verdik. Yani text özelliğini felan vermedik. Sütun nesnenin kendisini verdik. Şimdi bu işçilikin kalburüstü kısaca şu;

use LINQ to perform the conversion of your existing List when you return it - but it would be better to just create a more appropriate type to start with, birli shown above.

 

; being aware of the definition of the interface ie. all abstract methods that are there to be implemented by any class inheriting the interface. so if some one makes a huge class of his own with several methods besides the ones he inherited from the interface for some addition functionality, and those are of no use to you, its better to use a reference to a subclass (in this case the interface) and assign the concrete class object to it.

Then later if you decide to convert the actual veri store from a List to a Dictionary and expose the dictionary keys birli the actual C# IList Nasıl Kullanılır value for the property (I have had to do exactly this before). Then consumers who have come to expect that their changes will C# IList Nerelerde Kullanılıyor be reflected inside of your class will no longer have that capability. That's a big sıkıntı! If you expose the List birli an IEnumerable you can comfortably predict that your collection is not being modified externally. That is one of the powers of exposing List as any of the above interfaces.

Obviously if you are being asked which you use in an interview, you say IList, smile, and both look pleased at yourselves for being so clever. Or for a public facing API, IList. Hopefully you get my point.

Then I C# IList Neden Kullanmalıyız looked in my view(mvc) and found that I actually needed the count method as I needed to use a for loop. So in my own application I under estimated what I actually needed how do you anticipate what someone else will need or derece need.

If you use the concrete type all callers need to be updated. C# IList Nedir If exposed as IList the caller doesn't have to be changed.

IEnumerable allows you to iterate through a collection. ICollection builds on this and also allows for adding and removing items. IList also allows for accessing and modifying them at a specific index. By exposing C# IList Kullanımı the one that you expect your consumer to work with, you are free to change your implementation. List happens to implement all three of those interfaces. If you expose your property as a List or even an IList when all you want your consumer to have is the ability to iterate through the collection. Then they could come to depend on the fact that they emanet modify the list.