How to avoid memory leaks? When is the Garbage Collector not going to help you? How to make sure you implement IDisposable exactly right for your use case without falling into the “overdesign trap?” Explore those topics with a lot of practical examples. …
Category: .NET
When defining a generic interface, have you received a hint from Resharper like “The type parameter T could be declared as covariant” (or “contravariant”)? If so, have you then blindly applied the proposed refactoring which decorates your generic parameter with the in or out keyword? Like so: I know I’ve done this a few times before deciding to dig deeper into what these terms actually mean and how they affect my type’s behavior. Type variance is one of the topics …
FirstOrDefault() is one of the most (over)used IEnumerable extensions. Of course, it has its’ valid use cases not only semantically but sometimes from a performance perspective. In many cases, though, you can utilize alternative methods to convey your intentions more cleanly. …
Prefer constructor overloads or factory methods over implicit or explicit conversion operators. …
GetHashCode() is one of the functions you should probably avoid implementing yourself. It generates a lot of confusion among developers and can lead to some hard to track bugs when implemented poorly. The goal of this article is to help you understand the common mistakes developers make when implementing GetHashCode() and some general misconceptions when it comes to computing hash codes for your custom types in C#. Note that this is not a hash function design and implementation guideline. Rather, …