Comments on: LINQ in Depth: Understanding ToArray()

By: Christian

Christian — Sun, 05 Oct 2008 12:18:54 +0000

Well, the way i understand it, the use of buffer that needs to reallocate the size of the array is not unique to the second approach. The stringbuilder also works on an internal array, so to some extent the reallocation process will be a major part of what is taking time in both cases. However there are some factors that influence this and that maybe why your results are not completely conclusive. One major part is how much the array is expanded each time a reallocation occurs, and how many times this happens. Also string.join probably has some “special treatment” in the framework to help performance. Besides that the ToArray and String.Join probably both at the root require these kinds of operations, where your approach only requires reallocation of the array for the stringbuilder.

Anyway, its just my two cents, so now im broke..

By: Dew Drop - October 5, 2008 | Alvin Ashcraft's Morning Dew

Dew Drop - October 5, 2008 | Alvin Ashcraft's Morning Dew — Sun, 05 Oct 2008 12:13:50 +0000

[...] LINQ in Depth: Understanding ToArray() (Chris Brandsma) [...]

By: Steve

Steve — Sun, 05 Oct 2008 07:29:39 +0000

Thanks for trying this

sb.Remove(sb.Length – delimiter.Length, 1); should still be
sb.Remove(sb.Length – delimiter.Length, delimiter.Length);

Otherwise you only remove the first character of your delimiter.

For most uses it doesn’t matter then but I’ll keep it in mind when I have to use a lot of strings