The simplest way is probably by creating a temporary array:
list.AddRange(new T[size - count]);
Where size
is the required new size, and count
is the count of items in the list. However, for relatively large values of size - count
, this can have bad performance, since it can cause the list to reallocate multiple times.(*
) It also has the disadvantage of allocating an additional temporary array, which, depending on your requirements, may not be acceptable. You could mitigate both issues at the expense of more explicit code, by using the following methods:
public static class CollectionsUtil
{
public static List<T> EnsureSize<T>(this List<T> list, int size)
{
return EnsureSize(list, size, default(T));
}
public static List<T> EnsureSize<T>(this List<T> list, int size, T value)
{
if (list == null) throw new ArgumentNullException("list");
if (size < 0) throw new ArgumentOutOfRangeException("size");
int count = list.Count;
if (count < size)
{
int capacity = list.Capacity;
if (capacity < size)
list.Capacity = Math.max(size, capacity * 2);
while (count < size)
{
list.Add(value);
++count;
}
}
return list;
}
}
The only C# 3.0 here is the use of the "this
" modifier to make them extension methods. Remove the modifier and it will work in C# 2.0.
Unfortunately, I never compared the performance of the two versions, so I don't know which one is better.
Oh, and did you know you could resize an array by calling Array.Resize<T>
? I didn't know that. :)
Update:
(*
) Using list.AddRange(array)
will not cause an enumerator to be used. Looking further through Reflector showed that the array will be casted to ICollection<T>
, and the Count
property will be used so that allocation is done only once.