Variable argument function ambiguity

   public static void main(String[] args) {
       System.out.println(fun(2,3,4));
     }
   static int fun(int a,int b,int c)
   {
     return 1;
   }
   static int fun(int ... a)
   {
     return 0;  
   }

Output: 1

Question: In the above case why does the function fun select the 1st function and not the second.On what basis is the selection done since there is no way to determine开发者_高级运维 which fun the user actually wanted to call ?

Basically there's a preference for a specific call. Aside from anything else, this means it's possible to optimize for small numbers of arguments, avoiding creating an array pointlessly at execution time.

The JLS doesn't make this very clear, but it's in section 15.12.2.5, the part that talks about a fixed arity method being more specific than another method if certain conditions hold - and they do in this case. Basically it's more specific because there are more calls which would be valid for the varargs method, just as if there were the same number of parameters but the parameter types themselves were more general.

Compiler always selects the precise method when these kind of ambiguities are encountered. In your scenario func with three arguments is more precise than the variable arguments one so that is called.

EDIT: Edited as per skeet's comment.

If you test this expressions:

    System.out.println(fun(2,3,4));
    System.out.println(fun(2,3));
    System.out.println(fun(2,3,4,7));

The output is

1
0
0

The Java compiler first checks for a method whose declaration matchs the exact parameters of the invocation, and otherwise, it searches for the alternative method matching.

This behaviour allows the resolution of two overloaded variable argument calls:

addStates(String... states)
addStates(Enum... states)

Calling addStates() gives a compile ambiguity problem. Adding in a third method:

addStates(){
   addStates(new String[0]);
}

This allows selection selecting the more specific third addStates() to resolve the ambiguity problem of being unsure which of the variable type parameter methods to call.