driisdriis 163k4545 gold badges268268 silver badges343343 bronze badges 3 Sorry, but even now there are plenty of uses for library code to use IList (non-generic). Anyone who says otherwise hasn't suffered enough reflection / veri-binding / etc ;)
Bir dahaki sefere tefsir yaptığımda kullanılmak üzere etapı, e-posta adresimi ve web şehir adresimi bu tarayıcıevet kaydet.
lomaxxlomaxx 115k5858 gold badges146146 silver badges180180 bronze badges 1 Why would you return an IList in the first place? From a WCF service?
A List object allows you to create a list, add things to it, remove it, update it, index into it and etc. List is used whenever you just want a generic list where you specify object type in it and that's it.
Use whatever you want. It's your method. You're the only one who gets to see the internal implementation details of the method.
In some code this sevimli be quite important and using concrete classes communicates your intent, your need for that specific class. An interface on the other hand says "I just need to call this set of C# IList Neden Kullanmalıyız methods, no other contract implied."
Remove Silinmesini matlup kıymeti siler. Silinecek ayar liste süresince birden zait olması yerinde ilk değeri kaldırır. Bu metodu ekseriyetle referans tipler ile porte çıkarmak karınin kullanılır. Ancak fehamet tipleri C# IList Kullanımı ile de kullanılabilir.
If your methods form part of an interface, the methods will need to be C# IList Nedir defined using types available to that interface.
Whether you return an Interface or a concrete type depends upon what you want to let your callers do with the object you created -- this is an API design decision, and there's no hard and fast rule. You have to weigh their ability to make full use of the object against their ability to easily use a portion of the objects functionality (and of course whether you WANT them to be making full use of the object).
If you birey consider your method, determine that you probably won't be changing the return collection type, then it is probably safe to return a more exact C# IList Neden Kullanmalıyız type. If you aren't sure, or are afraid that if you change it in future you'll be breaking other people's code, then go more general.
Bir ahir elementin varlığını sınayan MoveNext ve geçerli elementi veren GetCurrent metodlarına sahiptir.
Less ridiculous way to prove that an Ascii character compares equal with itself in Coq more hot questions
List derslikı tanımlanırken T tip bileğmeselekenini kırmızıır. Kısaca listenin muhteviyatında hangi türden nesne yada bileğfiilkenlerin olacağını belirler.
I read a lot of posts C# IList Nasıl Kullanılır saying how this makes it easier to change the implementation later on, but I just don't fully see how that works.