tags:

views:

324

answers:

4

Do I really need to implement it myself?

private void shrinkListTo(ArrayList<Result> list, int newSize) {
  for (int i = list.size() - 1; i >= newSize; --i)
  list.remove(i);
}
+1  A: 

use ArrayList#removeRange() method:

protected void removeRange(int fromIndex, int toIndex)

Removes from this list all of the elements whose index is between fromIndex, inclusive, and toIndex, exclusive. Shifts any succeeding elements to the left (reduces their index). This call shortens the list by (toIndex - fromIndex) elements. (If toIndex==fromIndex, this operation has no effect.)

then use ArrayList#trimToSize() method:

Trims the capacity of this ArrayList instance to be the list's current size. An application can use this operation to minimize the storage of an ArrayList instance.

dfa
downvotes without explaination are pointless
dfa
protected method???
ripper234
if you cannot subclass, try subList (check my second answer)
dfa
+1  A: 

There is another consideration. You might want to shy away from using an ArrayList in your method signature, and instead work to the List interface, as it ties you into theArrayList implementation, making changes down the line difficult if you find that, for example, a LinkedList is more suitable to your needs. Preventing this tight coupling does come at a cost.

An alternative approach could look like this:

private void shrinkListTo(List<Result> list, int newSize) {
  list.retainAll(list.subList(0, newSize);
}

Unfortunately, the List.retainAll() method is optional for subclasses to implement, so you would need to catch an UnsupportedOperationException, and then do something else.

private void shrinkListTo(List<Result> list, int newSize) {
  try {
    list.retainAll(list.subList(0, newSize);
  } catch (UnspportedOperationException e) {
     //perhaps log that your using your catch block's version.
     for (int i = list.size() - 1; i >= newSize; --i)
        list.remove(i);
     }
  }
}

That is not as straight forward as your orginal. If you are not tied to the instance of the List that you are passing in, you could just as easily return a new instance by calling subList(int start, int end), and you wouldnt even need to make a method. This would also be a faster implementation, as (in Java 6), you would be getting an instance of an AbstractList.SubList that contains your list, an offset into it and a size. There would be no need for iterating.

If you are interested in the arguments for coding to Interfaces instead of classes, see this favorite article by Allen Holub

akf
using .retainAll() is going to be really inefficient. it will have to take O(n^2) because for each element of the list, it has to go through the sublist to check for it (it doesn't know that it's a sublist)
newacct
+5  A: 

Create a sublist With the range ofelements you wish to remove and then call clear on the returned list.

List.subList(23, 45).clear()
mP
+1 probably the fastest implementation that retains the pointer to the original
akf
+2  A: 

alternatively you can use subList method:

public static <T> List<T> shrinkTo(List<T> list, int newSize) {
    return list.subList(0, newSize - 1);
}
dfa
yea but this does not affect the original list. maybe the elements to be removed are no longer needed and he wants to free them; this method would not accomplish that.
newacct
the GC will take care of it
dfa