Skip to main content

Unlocking Collection Expressions for your own types

C# 12 introduced collection expressions, a new, simplified syntax for initializing collections:

This syntax works great with built-in collection types, but what about your own custom collections?

That's where CollectionBuilderAttribute comes in, allowing you to extend this modern syntax to your own types.

Custom Collections left behind

Imagine you've built a custom immutable collection type:

Before CollectionBuilderAttribute, you couldn't use the new collection expression syntax with this type. You'd be stuck with the old way:

Not exactly elegant compared to the modern syntax.

Enter CollectionBuilderAttribute

The CollectionBuilderAttribute bridges this gap by telling the compiler how to construct your collection from a collection expression. Here's an example:

Now you can write:

Beautiful! The compiler automatically calls your Create method with the items.

How it works

The attribute takes two parameters:

  1. Builder Type: A type containing the factory method (typeof(ImmutableStackBuilder))
  2. Method Name: The name of the static method that creates instances ("Create")

The builder method must:

  • Be static
  • Accept either ReadOnlySpan<T> (preferred) or T[]
  • Return an instance of your collection type
  • Have generic type parameters matching your collection

Remark: it is also necessary that the collection is an "iteration type", i.e. it should have a GetEnumerator() method that returns an IEnumerator (or IEnumerator<T>). The typical way to achieve this is by implementing the IEnumerable or IEnumerable<T> interface.

When all these things are in place, the compiler can generate the necessary code to construct your collection in the most efficient way.

More information

Collection expressions (Collection literals) - C# reference | Microsoft Learn

Adding support for collection expressions to yor own types

CollectionBuilderAttribute Class (System.Runtime.CompilerServices) | 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) ...

The role of ActivitySource in OpenTelemetry for .NET

While doing some pair programming to integrate OpenTelemetry tracing to a .NET application, we had a discussion on how to use the ActivitySource . It looks simple. You new one up, give it a name, start an activity, done. The discussion started when we added a second ActivitySource with the exact same name in a different class. This made us wonder: "Are we duplicating traces now? Is this a memory leak? Do we need a singleton?" So we decided to dig deeper. This post is what we learned… What ActivitySource actually is ActivitySource is part of System.Diagnostics , not part of the OpenTelemetry NuGet packages. Microsoft built tracing primitives directly into the BCL, and OpenTelemetry's .NET SDK simply listens to them. This is why you can add distributed tracing to a library without taking a dependency on OpenTelemetry at all. An ActivitySource is a factory for Activity objects, and an Activity is .NET's name for what OpenTelemetry calls a span.(don’t ask m...