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.
Bir dahaki sefere versiyon yapmış olduğumda kullanılmak üzere kademı, elektronik posta adresimi ve web kent adresimi bu tarayıcıya kaydet.
If someone passes you an Array or a List, your code will work fine if you check the flag every time and have a fallback... But really; who does that?
Remove Silinmesini matlup değeri siler. Silinecek mesabe liste ortamında birden aşkın olması yerinde ilk değeri kaldırır. Bu metodu umumiyetle referans tipler ile haysiyet çıkarmak bâtınin kullanılır. Ama kırat tipleri ile bile kullanılabilir.
Your code is now broken, because int[] implements IList, but is of fixed size. The contract for ICollection (the base of IList) requires the code that uses it to check the IsReadOnly flag before attempting to add or remove items from the collection. The contract for List does hamiş.
You can have an instance of an interface, but you need to initialize it with a class that C# IList Neden Kullanmalıyız implements that interface such bey:
In case of using IList, the caller is always guareented things to work, and the implementer is free to change the underlying collection to any alternative C# IList Neden Kullanmalıyız concrete implementation of IList
If you specify your methods to return an interface that means you are free to change the exact implementation later C# IList Kullanımı on without the consuming method ever knowing.
One Piece Şeytan Meyveleri Kitabı ile anime yazılarımıza devam C# IList Nedir edelim. Önceleri toparladığım bir ovaydı bu yazı. Bir anime izlerken o animeyi ne kadar çok sevdiğime…
It really comes down to the kind of functionality you need. I'd suggest using the List class in most cases. IList is best for when you need to make a custom array that could have some very specific rules that you'd like to encapsulate within a collection so you don't repeat yourself, but still want .NET to recognize it bey a list.
private List _numbers; // callers birey add/update/remove elements, but cannot reassign a new list to this property
Bu örnekte, Student isminde bir derslik ve StudentCollection isminde CollectionBase klasından türeyen özel bir koleksiyon derslikı oluşturduk.
So typically, your methods should accept and return interfaces for collections. This C# IList Nedir leaves your own implementation and your callers room to decide on the actual implementation birli required.
This works, because only the outer list is created in the first place. You gönül then insert individual items that are compatible with IList: