Why does type-promotion take precedence over varargs for overloaded methods

by

JLS 15.12.2 is the relevant bit of the spec to look at here. In particular – emphasis mine:

The remainder of the process is split into three phases, to ensure compatibility with versions of the Java programming language prior to Java SE 5.0. The phases are:

  • The first phase (§15.12.2.2) performs overload resolution without permitting boxing or unboxing conversion, or the use of variable arity method invocation. If no applicable method is found during this phase then processing continues to the second phase.

    This guarantees that any calls that were valid in the Java programming language before Java SE 5.0 are not considered ambiguous as the result of the introduction of variable arity methods, implicit boxing and/or unboxing. However, the declaration of a variable arity method (§8.4.1) can change the method chosen for a given method method invocation expression, because a variable arity method is treated as a fixed arity method in the first phase. For example, declaring m(Object...) in a class which already declares m(Object) causes m(Object) to no longer be chosen for some invocation expressions (such as m(null)), as m(Object[]) is more specific.

  • The second phase (§15.12.2.3) performs overload resolution while allowing boxing and unboxing, but still precludes the use of variable arity method invocation. If no applicable method is found during this phase then processing continues to the third phase.

    This ensures that a method is never chosen through variable arity method invocation if it is applicable through fixed arity method invocation.

  • The third phase (§15.12.2.4) allows overloading to be combined with variable arity methods, boxing, and unboxing.

In your case, the first phase finds a match without using variable arity method invocation or boxing, hence that’s the result. As noted in the spec, this is basically for backward compatibility.

More Related Contents:

  1. bug with varargs and overloading?
  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. foo(int) is not applicable for the arguments (String)
  6. Does Java support default parameter values?
  7. What do 3 dots next to a parameter type mean in Java?
  8. Properly removing an Integer from a List
  9. Can I pass an array as arguments to a method with variable arguments in Java?
  10. What is the difference between method overloading and overriding? [duplicate]
  11. How is an overloaded method chosen when a parameter is the literal null value?
  12. What is the difference between dynamic and static polymorphism in Java?
  13. What is the point of overloaded Convenience Factory Methods for Collections in Java 9
  14. Can I override and overload static methods in Java?
  15. Reference is ambiguous with generics
  16. Overloading in Java and multiple dispatch
  17. Strange Java null behavior in Method Overloading [duplicate]
  18. Java – why no return type based method overloading?
  19. Lambda expression and method overloading doubts
  20. Java erasure with generic overloading (not overriding)
  21. Accessing constructor of an anonymous class
  22. Ambiguous varargs methods
  23. Java method overloading + double dispatch
  24. Java varargs method param list vs. array
  25. Java “params” in method signature?
  26. Java overloading rules
  27. How to do method overloading for null argument?
  28. Calling base class overridden function from base class method
  29. Why varargs should be the last in a method signature?
  30. Overriding a method with different return types in java?

Leave a Comment