I do not pass around Listss if I can possibly help it. Generally I have something else that is managing the collection in question, which exposes the collection, for example:
In EF Core, you güç encapsulate collections and achieve true domain modeling by using backing fields.
Ayrıca, yazılımınızın performansını bırakmak muhtevain metotları optimize edebilir ve kodun henüz hızlı çkızılışmasını esenlayabilirsiniz.
Birli you suggest, my intention is only to protect the collection from direct modification; the collection members are not going to be modified (or needed to be modified).
The IReadOnlyDictionary interface provides a read-only view of a dictionary and represents a read-only collection of key/value pairs. The following code snippet illustrates how you emanet define an IReadOnlyDictionary instance.
You want to use the yield keyword. You loop through the IEnumerable list and return the results with yeild. This allows the consumer to use the for each without modifying the collection.
Thous leads that your consumer classes are just awaiting interfaces instead of concrete classes and so you emanet change the concrete implementation at a later stage without C# ReadOnlyCollectionBase Nerelerde Kullanılıyor breaking your public contract (due to performance reasons use an List instead of a LinkedList or vice versa).
Average(IEnumerable, Func) Computes the average of a sequence of nullable Decimal values that are obtained by C# ReadOnlyCollectionBase Nedir invoking a transform function on each element of the input sequence.
C# IStructuralEquatable arabirimini C# ReadOnlyCollectionBase Kullanımı uygulayan bir özel derme klası oluşturarak, nasıl konstrüktif eşitlik kontrolörü kuruluşlacağını anlamak önemlidir. Bayağıdaki örnek, C# ReadOnlyCollectionBase Nasıl Kullanılır bu konuyu daha yararlı anlamanıza yardımcı olacaktır:
If you do this then there's nothing stopping your callers casting the IEnumerable back to ICollection and then modifying it. ReadOnlyCollection removes this possibility, although it's still possible to access the underlying writable collection via reflection.
Nothing wrong with wordy types for major API's with small surfaces, but derece kakım a general practice inside a large codebase.
However, to be doubly sure, I'd like to return the collection as read-only, so that the calling code is unable to make changes to the collection, only view what's already there. Is this at all possible?
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Initializes a new C# ReadOnlyCollectionBase Temel Özellikleri instance of the ReadOnlyCollection class that is a read-only wrapper around the specified list.