Just a very short blog post... for everyone who is not yet known to it. Since .Net Framework 4.6 for two immutable types we got new static fields in the framework:
<ul>
<li><a target="_blank" href="https://learn.microsoft.com/en-us/dotnet/api/system.array.empty?view=netframework-4.6">Array.Empty&lt;T&gt;</a>
</li>
<li><a target="_blank" href="https://learn.microsoft.com/en-us/dotnet/api/system.string.empty?view=net-8.0">string.Empty</a>
</li>
</ul>
<pre><code class="lang-csharp">// instead of
string foo = "";
byte[] bar = new byte[0];

// prefer
string foo = string.Empty;
byte[] bar = Array.Empty&lt;byte&gt;();
</code></pre>
If you are now asking yourself why you should use this - string and array are immutable (they will always be created new when the content does change and the old memory is garbaged). By using the static fields there is no additional memory location for the value of the variable, it will always be the same.
Naturally, you will first note a real impact if you are creating very much strings and/or arrays. But it is always better to follow best practices from the beginning instead of running into problems afterwards...

Just a very short blog post... for everyone who is not yet known to it. Since .Net Framework 4.6 for two immutable types we got new static fields in the framework:

* [Array.Empty&lt;T&gt;](https://learn.microsoft.com/en-us/dotnet/api/system.array.empty?view=netframework-4.6)
 
* [string.Empty](https://learn.microsoft.com/en-us/dotnet/api/system.string.empty?view=net-8.0)
 

```csharp
// instead of
string foo = "";
byte[] bar = new byte[0];

// prefer
string foo = string.Empty;
byte[] bar = Array.Empty<byte>();
```

If you are now asking yourself why you should use this - string and array are immutable (they will always be created new when the content does change and the old memory is garbaged). By using the static fields there is no additional memory location for the value of the variable, it will always be the same.

Naturally, you will first note a real impact if you are creating very much strings and/or arrays. But it is always better to follow best practices from the beginning instead of running into problems afterwards...

Empty string and array best practices in C#