using LinkDotNet.StringBuilder; // Namespace of the package
ValueStringBuilder stringBuilder = new ValueStringBuilder();
stringBuilder.AppendLine("Hello World");
string result = stringBuilder.ToString();
There are also smaller helper functions, which enable you to use ValueStringBuilder without any instance:
The dotnet version of the StringBuilder is an all-purpose version that normally fits a wide variety of needs.
But sometimes, low allocation is key. Therefore I created the ValueStringBuilder. It is not a class but a that tries to allocate as little as possible.
If you want to know how the works and why it uses allocations and is even faster, check out blog post.
The blog goes into a bit more in detail about how it works with a simplistic version of the .
The library is not meant as a general replacement for the StringBuilder shipped with the .net framework itself. You can head over to the documentation and read about the "Known limitations".
The library works best for a small to medium amount of strings (not multiple 100'000 characters, even though it can be still faster and uses fewer allocations). At any time, you can convert the ValueStringBuilder to a "normal" StringBuilder and vice versa.
The normal use case is to concatenate strings in a hot path where the goal is to put as minimal pressure on the GC as possible.
Documentation
More detailed documentation can be found here. It is really important to understand how the ValueStringBuilder works so that you did not run into weird situations where performance/allocations can even rise.
Benchmark
The following table gives you a small comparison between the StringBuilder which is part of .NET and the ValueStringBuilder:
