Skip to main content

Type Aliases in C#: Bringing F#-style readability to your C# code

As I like to to program not only in C# but also F#, there are some paradigms and features in F# that influence my C# coding style. One of those features is F# type abbreviations that make complex type signatures more understandable and expressive. Since C#12, you have a similar feature available in C#: type aliases using the using directive.

But although this option already exists for some time, I don’t see many C# developers use it. But I’ll hope that this blog post can help to change this and increase adoption…

What are Type Aliases?

Type aliases allow you to create shorthand names for existing types, making your code more readable and self-documenting. Instead of repeatedly writing complex generic types or lengthy class names, you can define a meaningful alias that captures the intent of your data structure.

The F# connection

In F#, type abbreviations have been a feature for years:

These abbreviations don't create new types—they're simply aliases that make the code more expressive and easier to understand.

C# Type Aliases in action

C# 12 brings this capability to C# developers through enhanced using statements at the file level:

For me type aliases really shine in domain-driven design where you want to avoid primitive obsession and be more explicit:

Benefits and limitations

The benefits of using (no pun intended) this feature are obvious:

  • Improved readability: Code becomes self-documenting
  • Reduced cognitive load: Less mental parsing of complex type signatures
  • Better refactoring: Change the underlying type in one place
  • Domain clarity: Express business concepts more clearly in code

Unfortunately compared to F# type abbreviations, C# type aliases still have some limitations:

  • File scope only: Aliases are limited to the file where they're declared
  • No type safety: Aliases don't create distinct types—they're purely cosmetic
  • No IntelliSense benefits: The underlying type still appears in tooltips and errors

While they don't provide the same level of type safety as distinct types, they offer a lightweight way to make your code more readable and self-documenting.

More information

Alias any type - C# feature specifications | Microsoft Learn

Type Abbreviations - F# | 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) ...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.