Note that the IsReadOnly flag comes from ICollection, and indicates whether items sevimli be added or removed from the collection; but just to really confuse things, it does hamiş indicate whether they dirilik be replaced, which in the case of Arrays (which return IsReadOnlys == true) güç be.
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.
Elemanların Sıralı Yapkaloriı Sahabet: IList, elemanların eklenme sırasını korur. Bu özellik, done yapkaloriın sıralı olmasını ve programın beklentilerine mütenasip çalışmasını sağlar.
Then click on the bulb symbol or place the cursor on the IList and press Strg + "." You will become several implementations offered, like:
Basically, I need to see some actual code examples of how using IList would have solved some sıkıntı over just taking List into everything.
so its safety for you and freedom to the coder who is writing concrete implementation to change or add more functionality to his concrete class.
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, as shown above.
If C# IList Neden Kullanmalıyız the collection is indexed, the indexes of the elements that are moved are also updated. This behavior does not apply to collections where elements are conceptually grouped into C# IList Nerelerde Kullanılıyor buckets, such bey a hash table.
For example, let's say you have a Person class and a Group class. A C# IList Nedir Group instance katışıksız many people, so a List here would make sense. When I declare the list object in Group I will use an IList and instantiate it as a List.
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 value for the property (I have had to do exactly this before). Then consumers who have come to expect that their changes will be reflected inside of your class will no longer have that capability. That's a big mesele! If you expose the List bey an IEnumerable you gönül 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.
This argument only works if you write your own implementation of IList from sratch (or at least without inheriting List)
I leave this up to show that if you needed to do it (e.g. the off chance a third party library returned a List that you needed to convert for another 3rd party library), you sevimli do it this way.
List derslikı tanımlanırken T tip bileğustalıkkenini tuzakır. Doğrusu listenin içeriğinde ne türden nesne yada değmaslahatkenlerin olacağını belirler.
It doesn't affect the signature of the method, and is grup in stone at compile time. You should C# IList Nerelerde Kullanılıyor instead C# IList Neden Kullanmalıyız be helping him get over his confusion about declaring his local like IList foo = new List - this is where his confusion clearly lies.