Home/ Questions/Q 607015
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T17:18:54+00:00

I’m wondering if this code … StringBuilder sb = new StringBuilder(Please read the following

  • 0

I’m wondering if this code …

StringBuilder sb = new StringBuilder("Please read the following messages.");

… initializes sb with a buffer exactly as large as the string passed to the constructor. On the one hand, this would seem the most logical thing. On the other hand, it seems to kind of defeat the purpose of the StringBuilder class for one of its most common uses, which is to provide mutability to make repeated appends more efficient. (The very first call to Append, if the answer to my question is “yes”, would require sb to resize itself.)

Then again, I suppose one could view this as analogous to the constructor for List<T> that takes an IEnumerable<T> as a parameter. Maybe the assumption in this case is that you’re not planning on appending a lot, but rather on manipulating what’s already there.

The only real research I’ve done on this was to check the MSDN documentation on StringBuilder, which didn’t provide an answer (it says the constructor initializes the instance “using the specified string,” but doesn’t indicate how the string is used).

EDIT: So it’s “implementation-specific”… does this not seem weird to anyone else? I mean, the purpose of the StringBuilder class is to offer an alternative to performing a lot of operations on a string, creating a ton of immutable string instances along the way; therefore, it’s for efficiency. I feel like the behavior of this constructor ought the be specified, so that the developer can make an informed decision how to use it regardless of platform.

I mean, it is implemented by Microsoft a certain way; they could easily have put that in the documentation (forcing other implementations to follow suit). Just a personal source of puzzlement…

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It’s an implementation detail that you shouldn’t need to worry about. However, using .NET reflector, and looking in the (string,int32,int32,int32) overload of the constructor (which the other constructors call), we can see that it picks a capacity that is a multiple of 16 (next largest over the requested size)

    Edit

    Actually, it’s 16 x 2^n, with the value of “n” selected to be the next largest size

    • 0