The "JDK 11 Early-Access Release Notes" indicate that Early Access Build 20 of JDK 11 includes a new default method on the Collection interface that "allows the collection's elements to be transferred to a newly created array of the desired runtime type." This new default method, Collection.toArray(IntFunction), works similarly to the same-named method already available on the Stream interface, Stream.toArray(IntFunction).

The next code listing demonstrates a new JDK 11 default Collection method in action (on a Set in this case).

final Set<String> names = Set.of("Fred", "Wilma", "Barney", "Betty");  
out.println(Arrays.toString(names.toArray(String[]::new)));  

Because I used an (unordered) set, the order of the String in the generated array can be different than the order of the Stringspecified for initialization of the Set. This is demonstrated in the next screen snapshot. This also indicates that I'm using JDK 11 Early Access Build 23 for this example).

Many of us use the Java collections more frequently than arrays, but there are times when we need to convert these collections to arrays. The default method Collection.toArray(IntFunction) provides a highly convenient mechanism for this. There was already a similar method on Collecton,Collection.toArray(T[]), and the existence of these two methods means that it is no longer possible to pass null to the Collection.toArray(-) method. During this, the compiler is unable to distinguish them and will report the error message "reference to toArrayis ambiguous." This is not much of a price to pay since both methods throw a NullPointerException anyway when null is passed to them.