I know there özgü been a lot of posts on this but it still confuses me why should you pass in an interface like IList and return an interface like IList back instead of the concrete list.
Maybe take it into a List of T rather than ArrayList, so that you get type safety and more options for how you implement the comparer.
Diyelim ki formunuzdaki textboxları listenize doldurdunuz sadece Text’i boş olan textboxları bulmanız gerekiyor. Bunun yürekin List u kullanmanız gerekir. Yukarıda anlattığımız örneği kolay olarak meydana getirecek olursak;
Remove Silinmesini istenilen değeri siler. Silinecek kadir liste süresince yekten lüks olması yerinde ilk kıymeti kaldırır. Bu metodu ekseriyetle referans tipler ile kıymet çıkarmak yürekin kullanılır. Lakin haysiyet tipleri ile bile kullanılabilir.
swilliamsswilliams 48.6k2727 gold badges101101 silver badges130130 bronze badges 3 5 why not make it a just a List in the first place? I still don't understand why bonus you get from making it a IList then in the constructor you make it into a List
In some code this gönül 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 takım of methods, no other contract implied."
List implements IList, and so birey be assigned to the variable. There are also other types that also implement IList.
In VS2008, when I click on the service reference C# IList Neden Kullanmalıyız and select "Configure Service Reference", there is an option to choose how the client de-serializes lists returned from the service.
If you yaşama consider your method, determine that you probably won't be changing the return collection type, then it is probably safe to C# IList Neden Kullanmalıyız return a more exact type. If you aren't sure, or are afraid that if you change it in future you'll be breaking other people's code, C# IList Nerelerde Kullanılıyor then go more general.
I know that IList is the interface and List is the concrete type but C# IList Neden Kullanmalıyız I still don't know when to use each one. What I'm doing now is if I don't need the Sort or FindAll methods I use the interface. Am I right? Is there a better way to decide when to use the interface or the concrete type?
Then I 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 C# IList Neden Kullanmalıyız you anticipate what someone else will need or not need.
Dizin tarafından erişilebilen nesnelerin mutlak olarak belirlenmiş bir listesini simgeleme eder. Listeleri kontrol, sıralama ve işleme şekilleri sağlar.
There is a complication though that dynamic hayat't see explicit implementations, so something yaşama implement IList and IList-of-T and yet still be completely unusable from dynamic.