Dealing with empty lists is an everyday situation in .NET. An empty list is often preferred to a null in order to control the logic. But how expensive is it to return an empty list?
The options
A List can currently - .NET 9 - be initialized in several ways
| Variant | Description |
|---|---|
new List() | Creates a list with the default capacity 0 |
new List(0) | Creates a list with the default capacity 0 |
new List(1) | Creates a list with the default capacity 4 |
new List(31) | Creates a list with the default capacity 31 |
[] | Creates a list with the default capacity 0 |
The notation [] is the latest and currently recommended notation. This is because this applies not only to List, but to all .NET collections.
In contrast to List, the most efficient option is not the constructor, but Array.Empty. [] for arrays is therefore an alias for Array.Empty.
Benchmark
The benchmark
shows very clearly why [] is the recommended spelling: it always guarantees the most efficient solution.
1BenchmarkDotNet v0.13.12, Windows 10 (10.0.19045.4651/22H2/2022Update)
2AMD Ryzen 9 5950X, 1 CPU, 32 logical and 16 physical cores
3.NET SDK 9.0.100-preview.5.24307.3
4 [Host] : .NET 9.0.0 (9.0.24.30607), X64 RyuJIT AVX2
5 .NET 9.0 : .NET 9.0.0 (9.0.24.30607), X64 RyuJIT AVX2
6
7| Method | Mean | Ratio | Gen0 | Allocated |
8|------------ |----------:|------:|-------:|----------:|
9| List() | 2.7975 ns | 1.00 | 0.0019 | 32 B |
10| List(0) | 2.9224 ns | 1.04 | 0.0019 | 32 B |
11| List [] | 2.7643 ns | 0.99 | 0.0019 | 32 B |
12| Array.Empty | 0.4912 ns | 0.18 | - | - |
13| Array [] | 0.4835 ns | 0.18 | - | - |
14| HashSet() | 4.0250 ns | 1.48 | 0.0038 | 64 B |
15| HashSet [] | 4.0798 ns | 1.46 | 0.0038 | 64 B |The bechmark: https://github.com/BenjaminAbt/SustainableCode/tree/main/csharp/list-empty-return
Related articles
- 11 min read
Containerizing .NET in 2026 Without a Dockerfile
Most .NET Dockerfiles repeat the same five steps: restore, publish, select the matching Microsoft runtime image, copy the output and start …
- 12 min read
Problem Details in ASP.NET Core and .NET 11
builder.Services.AddProblemDetails() registers infrastructure. It does not create an error contract. An ASP.NET Core request can fail during …
- 11 min read
Resilience in .NET with Microsoft.Extensions.Resilience
Retries are the most visible resilience strategy and the easiest one to misuse. Repeating a failing call can recover from a short network …
BEN ABT
Ben is Chief Engineering Officer and Principal Software Engineer at Medialesson.de, with a strong focus on .NET and Microsoft Azure. In his professional role, he designs and builds highly scalable platforms for hybrid and cloud-based scenarios. He also advises companies and C-levels on migrating to the sovereign cloud.
He runs myCSharp.de, the largest and most active German-speaking C# community forum, actively contributes to both his own and external open-source projects and regularly shares his knowledge through his blog, at community events, conferences and as a writer for technical magazines.
Let's Work Together
Looking for an experienced Platform Architect or Engineer for your next project? Whether it's cloud migration, platform modernization or building new solutions from scratch - I'm here to help you succeed.