Skip to end of metadata
Go to start of metadata

A variable arity (aka varargs) method is a method that can take a variable number of arguments. The method must contain at least one fixed argument. When processing a variable arity method call, the Java compiler checks the types of all arguments, and all of the variable actual arguments must match the variable formal argument type. However, compile-time type checking is ineffective when Object or generic parameter types are used [Bloch 2008]. The presence of initial parameters of specific types is irrelevant; the compiler will remain unable to check Object or generic variable parameter types. Enable strong compile-time type checking of variable arity methods by using the most specific type possible for the method parameter.

Noncompliant Code Example (Object)

This noncompliant code example sums a set of numbers using a variable arity method that uses Object as the variable arity type. Consequently, this method accepts an arbitrary mix of parameters of any object type. Legitimate uses of such declarations are rare (but see the "Applicability" section of this guideline).

double sum(Object... args) {
   double result = 0.0;
   for (Object arg : args) {
     if (arg instanceof Byte) {
       result += ((Byte) arg).byteValue();
     } else if (arg instanceof Short) {
       result += ((Short) arg).shortValue();
     } else if (arg instanceof Integer) {
       result += ((Integer) arg).intValue();
     } else if (arg instanceof Long) {
       result += ((Long) arg).longValue();
     } else if (arg instanceof Float) {
       result += ((Float) arg).floatValue();
     } else if (arg instanceof Double) {
       result += ((Double) arg).doubleValue();
     } else {
       throw new ClassCastException();
   return result;

Compliant Solution (Number)

This compliant solution defines the same method but uses the Number type. This abstract class is general enough to encompass all numeric types, yet specific enough to exclude nonnumeric types.

double sum(Number... args) {
  // ...

Noncompliant Code Example (Generic Type)

This noncompliant code example declares the same variable arity method using a generic type parameter. It accepts a variable number of parameters that are all of the same object type; however, it may be any object type. Again, legitimate uses of such declarations are rare.

<T> double sum(T... args) {
  // ...

Compliant Solution (Generic Type)

This compliant solution defines the same generic method using the Number type.

<T extends Number> double sum(T... args) {
  // ...

Be as specific as possible when declaring parameter types; avoid Object and imprecise generic types in variable arity methods. Retrofitting old methods containing final array parameters with generically typed variable arity parameters is not always a good idea. For example, given a method that does not accept an argument of a particular type, it could be possible to override the compile-time checking—through the use of generic variable arity parameters—so that the method would compile cleanly rather than correctly, causing a runtime error [Bloch 2008].

Also, note that autoboxing prevents strong compile-time type checking of primitive types and their corresponding wrapper classes. For instance, this compliant solution produces the following warning but works as expected: warning: [unchecked] Possible heap pollution from parameterized vararg type T
<T extends Number> double sum(T... args) {


Injudicious use of variable arity parameter types prevents strong compile-time type checking, creates ambiguity, and diminishes code readability.

Variable arity signatures using Object and imprecise generic types are acceptable when the body of the method lacks both casts and autoboxing and it also compiles without error. Consider the following example, which operates correctly for all object types and type-checks successfully:

<T> Collection<T> assembleCollection(T... args) {
  return new HashSet<T>(Arrays.asList( args));

In some circumstances, it is necessary to use a variable arity parameter of type Object.  A good example is the method java.util.Formatter.format(String format, Object... args), which can format objects of any type.

Automated detection is straightforward.


[Bloch 2008]

Item 42, "Use Varargs Judiciously"

[Steinberg 2008]

"Using the Varargs Language Feature"

[Oracle 2011b]




  1. I think java.util.Formatter may also qualify as an exception to this rule. Sometimes you have to use Object... as an argument type.

  2. I'm wondering if we should add an example, or modify an existing example, to have additional fixed parameter types to show that it is not only this specific method signature but any use of a generic or Object type in a vararg method?

  3. I talked to Fred about this, but maybe make this more generic?  Don't use generic types when specific types will do?  And then show the body of the bad methods, so we know why they are bad.

  4. For the moment, I've left this referring just to variable arity parameters, but fixed the other points (I hope).

    • This has left me confused because in the applicability it is shown that the 2nd NCE is actually good
    • There is no body for the method in the 2nd NCE so I can't determine anything
    1. Addressed both comments (by revamping code examples)

  5. I can't understand this sentence:

    The Java compiler checks the type of the arguments to each variable arity (varargs) method to ensure that the arguments are of the same type or object reference.

    The same type as what?  "or object reference" just seems to be randomly added here.  Is this saying that all argument to arity functions need to be of the same type?

    1. Expanded that initial sentence; should be clearer now.