Skip to main content

Impress your colleagues with your knowledge about..the PrintMembers method

Sometimes when working with C# you discover some hidden gems. Some of them very useful, other ones a little bit harder to find a good way to benefit from their functionality. One of those hidden gems that I discovered some days ago is the PrintMembers method.

Record Types

To explain where you can find this method, I first have to talk about record types.  Record types were introduced in C# 9 as a new reference type that you can create instead of classes or structs. C# 10 adds record structs so that you can define records as value types.

Records are distinct from classes in that record types use value-based equality. Two variables of a record type are equal if the record type definitions are identical, and if for every field, the values in both records are equal.

Record types have a compiler-generated ToString method that displays the names and values of public properties and fields:

Person{ FirstName = Bart, LastName = Wullems }

In an application we are building we are using this ToString() method to generate a cache key. This works great until you add another reference type to your record type:

If we now print out the value, we see the following:

Product { FirstName = Bart, LastName = Wullems, PhoneNumbers = System.String[] }

We no longer have uniqueness what doesn’t make it a good cache key anymore.

PrintMembers

Let’s fix this by implementing a PrintMembers method on our record type.

Important! If you want to do this,  you need to be aware about the following:

  • For a sealed record that derives from object (doesn't declare a base record): private bool PrintMembers(StringBuilder builder);
  • For a sealed record that derives from another record (note that the enclosing type is sealed, so the method is effectively sealed): protected override bool PrintMembers(StringBuilder builder);
  • For a record that isn't sealed and derives from object: protected virtual bool PrintMembers(StringBuilder builder);
  • For a record that isn't sealed and derives from another record: protected override bool PrintMembers(StringBuilder builder);

Here is the implementation for our Person class:

If we now print out the value,  all the values are included:

Product { FirstName = Bart, LastName = Wullems, PhoneNumbers = 123/45.67.89,987/65.43.21 }

Nice!

More information:

Records - C# reference | Microsoft Learn

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...

A complex system designed from scratch never works

A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...