Question

I am wondering why did they design the toArray method in ArrayList to take a input of an array in Java?

    ArrayList<String> listArray = new ArrayList<String>();

    listArray.add("Germany");
    listArray.add("Holland");
    listArray.add("Sweden");

    String []strArray = new String[3];
    String[] a = (String [])listArray.toArray(strArray);

To me it appears that, they dont need this input because the instance of the ArrayList itself has enough details to convert the data into an array.

My question is why do they still need the array to be passed in? Thanks.

Answer 1

Two reasons I can think of:

1. Erasure means that the generic parameters aren’t available at runtime, so an ArrayList<String> doesn’t know that it contains strings, it’s just the raw type ArrayList. Thus all invocations of toArray() would have to return an Object[], which isn’t strictly correct. You’d have to actually create a second array of String[] then iterate over the first, casting all of its parameters in turn to come out with the desired result type.
2. The way the method is defined means that you can pass in a reference to an existing array, and have this populated via the method. In some cases this is likely very convenient, rather than having a new array returned and then copying its values elsewhere.