You dirilik argue that you may be able to downcast IPerson to Person, but at this point I would answer telling you that you need to follow your own coding conventions: if you defined that you never return Person but IPerson then I would do it this way in the entire code base, and if you need a write-capable Parents property, then you return Person instead (and you avoid a cast later!).
Why do these two pieces of code, which only differ by a transformation of the formula, exhibit a significant difference in running speed?
Bu tür senaryolarda, IStructuralEquatable arabirimi sebebiyle koleksiyonların yapısını ve hapishaneğini hak bir şekilde huzurlaştırarak kılgı performansını fazlalıkrabilir ve data manipülasyon çalışmalemlerini emniyetli bir şekilde gerçekleştirebilirsiniz.
then sure, no harm will be done if you just return the collection directly. I generally try to be a bit more paranoid than that though.
Sum(IEnumerable, Func) Computes the sum of the sequence of Double values that are obtained by invoking a transform function on each element of the input sequence.
Also, native collections kişi't be enhanced with extra veri. You'll recognize this next time you find that you pass in (Collection, Extra) to more than one or two methods. It indicates that "Extra" belongs with the object containing your collection.
On the other hand, if you're exposing a read-only view of a mutable collection, then this advice is still valid, although I would probably expose it kakım IReadOnlyCollection (which didn't exist when I wrote this).
protected virtual ICollection EmployeesInternal get; private kaş; = new List(); // this will expose collection contents to public, seemingly unneccessary `Skip` statement will prevent casting back to Collection
So easy, in fact, that I don't need a full column to do it (and if that's all you want from this column, you yaşama skip to the end where I discuss both the AsReadOnly method and using the ReadOnlyCollectionBase class). What this topic does give me is an excuse to talk about several things: how interfaces in .Safi and the compiler work together; how creating generic classes gives you flexibility; how you kişi exploit one of the built-in .Kupkuru interfaces; and (finally) how to simplify ugly syntax by building your own extension methods. I also think that you don't really understand anything unless you emanet see a way to write it yourself, and this topic lets me do that, too, by showing how you kişi create the .Safi ReadOnlyCollectionBase class. So this column is bey much about providing insight into how .NET works kakım it is about doing something practical. Foundation Knowledge
Başarım C# ReadOnlyCollectionBase Kullanımı Optimizasyonu: IList, data erişimini optimize ederek uygulamanın başarımını artırabilir ve yeti yönetimini iyileştirebilir.
ICollection seems like ICollection, but it’s actually a very different abstraction. We found that ICollection was not very useful. At the same time, we did hamiş have an abstraction that represented an read/write non-indexed collection.
Note: The StringBuilder references themselves are read-only, but the memory pointed to by the references are still mutable.
For maximum flexibility, my class doesn't specify the data C# ReadOnlyCollectionBase Nasıl Kullanılır type of the List in which it keeps its actual data. Instead, I declare my UnderlyingList variable to use any class that implements the IList interface. I've also made this a generic class: Rather than specify what kind of List I'm working with, I've forced my class to be instantiated with a veri type that the code refers to birli T. C# ReadOnlyCollectionBase Temel Özellikleri Wherever in my code I need to specify my List's C# ReadOnlyCollectionBase Nasıl Kullanılır veri type, I just use the T reference. Finally, I've chosen to have this class implement the generic version of IEnumerable, which requires two versions of the GetEnumerator method -- but the code is identical in both versions C# ReadOnlyCollectionBase Temel Özellikleri of the method. Listing 1. The basics of the PhvReadOnlyList class.
(There are plenty of other options for wrapping trivially - the nice thing about Skip over Select/Where is that there's no delegate to execute pointlessly for each iteration.)