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 / data-binding / etc ;)
Bu şekilde listelerin birbirini point etmesi ve ilişkilı listenin elemanlarına porte verilmesi sağlamlanmaktadır.
Using IList instead of List makes writing unit tests significantly easier. It allows you to use a 'Mocking' library to pass and return data.
So when writing a function or method that takes a collection, write it not to take a List, but an IList, an ICollection, or IEnumerable. The generic interfaces will still work even for heterogenous lists because System.
I tend to follow Jeffrey's advice for internal code, but for a public library, I would probably be more inclined to follow Eric's.
Buraya özen etmenizi istiyorum. Liste tipine textbox dedik ve listeye textbox eklerken de dikme nesne adını verdik. Doğrusu text özelliğini felan vermedik. Direk nesnenin kendisini verdik. Şimdi bu davranışin yalabık doğrusu şu;
The cost to do this is minimal, why not save yourself the headache later? It's what the interface principle is all about.
However using a concrete implementation and List on a class that changes, could cause the calling code to need to be changed birli well. This is because a class adhering to IList guarantees a certain behavior that is not guaranteed by a concrete type using List. Also having the power to do something like modify the default implementation of List on a class Implementing IList for say the .Add, .Remove or any other IList method gives the developer a lot
If you started with a concrete type and you decided to change to another one, even if it uses the same interface, you're going C# IList Neden Kullanmalıyız to break someone else's code unless you started off with an interface or abstract base type. Share Improve this answer Follow
Then later if you decide to convert the actual veri store from a List to a Dictionary and expose the dictionary keys as 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 C# IList Nasıl Kullanılır capability. That's a big sıkıntı! If you expose the List birli an IEnumerable you gönül comfortably predict that your collection is hamiş being modified externally. That is one of the powers of exposing List C# IList Nasıl Kullanılır as any of the above interfaces.
If you're working within a single method (or even in a single class or assembly in some cases) and no one outside is going to see what you're doing, use the fullness of a List. But if you're interacting with outside code, like when you're returning a list from a method, then you only want to declare the interface without necessarily tying yourself to a specific implementation, especially C# IList Kullanımı if you have no control over who compiles against your code afterward.
Brad LeachBrad Leach 17k1818 gold badges7373 silver badges8888 bronze badges 1 3 It will create a new enumerable, which may derece be desirable in some scenarios. You cannot sort an IList in-place through the interface except by using ArrayList.Adapter method in my knowledge.
You yaşama pass a plain array to something which accepts an IList parameter, and then you yaşama call IList.Add() and will receive a runtime exception:
additional advantage is that your code is safe from any changes to concrete class birli you are subscribing to only few of the methods of concrete class and those C# IList Nasıl Kullanılır are the ones that are going to be there birli long bey the concrete class inherits from the interface you are using.