The above is an IList itself kakım this is what seems to be the standard to use with nhibernate. Otherwise I might have returned IEnumberable back but hamiş sure. Still, I sevimli't figure out what the user would 100% need(that's where returning a concrete başmaklık an advantage over).
1 @supercat: What could ISortableList offer that's derece already in IList? Or, asked differently, why couldn't an IList be sorted in-place without re-adding the items by your imagined static method?
Important Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Dirilik a unique position be deduced if pieces are replaced by checkers (dirilik see piece color but not type)
Basically, I need to see some actual code examples of how using IList would have solved some mesele over just taking List into everything.
Convert your IList into List or some other generic collection and then you emanet easily query/sort it using System.Linq namespace (it will supply bunch of extension methods)
You are most often better of using the most general usable type, in this case the IList or even better the IEnumerable interface, so that you dirilik switch the implementation conveniently at a later time.
If you specify your methods to return an interface that means you are C# IList Nerelerde Kullanılıyor free to change the exact implementation later on without the consuming method ever knowing.
In VS2008, when I click on the service reference and select "Configure Service Reference", there is an option to choose how the client bile-serializes lists C# IList Neden Kullanmalıyız returned from the service.
Then later if you decide to convert the actual data store from a List to a Dictionary and expose the dictionary keys bey 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 problem! If you expose the List as an IEnumerable you gönül comfortably predict that your collection is C# IList Nerelerde Kullanılıyor derece being modified externally. That is one of the powers of exposing List as any of the above interfaces.
I know that IList is the interface and List is the concrete type but 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?
Muta Ambarlama: Uygulamalarda palyatif verileri yahut işleme sırasında oluşan verileri depolamak karınin kullanılabilir.
If you use a concrete implementation of list, another implementation of the same list C# IList Nasıl Kullanılır will not be supported by your code.
additional advantage is that your code is safe from any changes to concrete class kakım you are subscribing to only few of the methods of concrete class and those are the ones that are going to be there as long bey C# IList Kullanımı the concrete class inherits from the interface you are using.