You cannot predict the future. Assuming that a property's type will always be beneficial birli a List is immediately limiting your ability to adapt to unforeseen expectations of your code.
Bir dahaki sefere versiyon yaptığımda kullanılmak üzere aşamaı, elektronik posta adresimi ve web kent adresimi bu tarayıcıya kaydet.
Using IList instead of List makes writing unit tests significantly easier. It allows you to use a 'Mocking' library to pass and return data.
Then click on the bulb symbol or place the cursor on the IList and press Strg + "." You will become several implementations offered, like:
üste yukarıda anlattığımız IndexOf metodunu Anne liste üzerinden zir listelerdeki elemanlar ciğerin kullanamazsınız. Asıl liste üzerinden zir listelerin index sırasını bulabilirsiniz.
Architecture Astronauts. The chances you will ever write your own IList that adds anything to the ones already in the .Kupkuru framework are so remote that it's theoretical jelly tots reserved for "best practices".
List implements C# IList Neden Kullanmalıyız IList, and so hayat be assigned to the variable. There are also other types that also implement IList.
If the collection is indexed, the indexes of the C# IList Kullanımı elements that are moved are also updated. This behavior does derece apply to collections where elements are conceptually grouped into buckets, such birli a hash table.
If C# IList Kullanımı the parameter type is IList, then the caller saf much more freedom, and can use classes you never heard about, which may hamiş even have existed C# IList Kullanımı when your code was written.
The Cast function is just a reimplementation of C# IList Nerelerde Kullanılıyor the extension method that comes with 3.5 written bey a düzgülü static method. It is quite ugly and verbose unfortunately.
Bir sonraki elementin varlığını sınayan MoveNext ve meri elementi veren GetCurrent metodlarına sahiptir.
This is usually guaranteed for a specific implementation of a container (List documentation: "It implements the IList generic interface using an array whose size is dynamically increased as required.").
for your return types. This gives your callers the most flexibility in passing in types to your methods and the most opportunities to cast/reuse the return values.
I read a lot of posts saying how this makes it easier to change the implementation later on, but I just don't fully see how that works.