bug with varargs and overloading?

by

The problem is that it is ambiguous.

doIt(1, 2);

could be a call to doIt(int ...), or doIt(double ...). In the latter case, the integer literals will be promoted to double values.

I’m pretty sure that the Java spec says that this is an ambiguous construct, and the compiler is just following the rules laid down by the spec. (I’d have to research this further to be sure.)

EDIT – the relevant part of the JLS is “15.12.2.5 Choosing the Most Specific Method“, but it is making my head hurt.


I think that the reasoning would be that void doIt(int[]) is not more specific (or vice versa) than void doIt(double[]) because int[] is not a subtype of double[] (and vice versa). Since the two overloads are equally specific, the call is ambiguous.

By contrast, void doItAgain(int) is more specific than void doItAgain(double) because int is a subtype of double according the the JLS. Hence, a call to doItAgain(42) is not ambiguous.

EDIT 2 – @finnw is right, it is a bug. Consider this part of 15.12.2.5 (edited to remove non-applicable cases):

One variable arity member method named m is more specific than another variable arity member method of the same name if:

One member method has n parameters and the other has k parameters, where n ≥ k. The types of the parameters of the first member method are T1, . . . , Tn-1 , Tn[], the types of the parameters of the other method are U1, . . . , Uk-1, Uk[]. Let Si = Ui, 1<=i<=k. Then:

  • for all j from 1 to k-1, Tj <: Sj, and,
  • for all j from k to n, Tj <: Sk

Apply this to the case where n = k = 1, and we see that doIt(int[]) is more specific than doIt(double[]).

In fact, there is a bug report for this and Sun acknowledges that it is indeed a bug, though they have prioritized it as “very low”. The bug is now marked as Fixed in Java 7 (b123).

More Related Contents:

  1. Why does type-promotion take precedence over varargs for overloaded methods
  2. Varargs Java Ambiguous Call
  3. Varargs in method overloading in Java
  4. Why doesn’t autoboxing overrule varargs when using method overloading in Java 7?
  5. Does Java support default parameter values?
  6. Method Overloading for null argument
  7. What do 3 dots next to a parameter type mean in Java?
  8. Properly removing an Integer from a List
  9. When do you use varargs in Java?
  10. Overload with different return type in Java?
  11. Constructor overloading in Java – best practice
  12. Method overloading and choosing the most specific type
  13. How to properly match varargs in Mockito
  14. Possible heap pollution via varargs parameter
  15. varargs and the ‘…’ argument
  16. Why does String.valueOf(null) throw a NullPointerException?
  17. Reference is ambiguous with generics
  18. Lambda expression and method overloading doubts
  19. Method overload resolution in java
  20. Java variable number of arguments for a method
  21. Java erasure with generic overloading (not overriding)
  22. Why does Guava’s ImmutableList have so many overloaded of() methods?
  23. Ambiguous varargs methods
  24. How to work with varargs and reflection
  25. difference fn(String… args) vs fn(String[] args)
  26. Why varargs should be the last in a method signature?
  27. Java overloading and inheritance rules
  28. Java overloading vs overriding
  29. How do overloaded methods work?
  30. overloading method priority in java

Leave a Comment