Warn when 'null' argument may lead to "unexpected" overload resolution

[stephan-herrmann]

Warn when 'null' argument may lead to "unexpected" overload resolution

[iloveeclipse]

Not being compiler expert, just a "user", I would expect the compiler warns me if the following condition match: null passed to an argument that is overloaded (means, there are several candidates with different signatures that would match).

Examples :

• String.valueOf(null) matches both String.valueOf(Object) and String.valueOf(char[])
• List.of(null); matches both java.util.List.of(E) and java.util.List.of(E...)

In both cases above method chosen by compiler and runtime behavior don't match "naive" user expectations and so runtime errors are thrown, in opposite of what the user actually wanted.

[iloveeclipse]

From the user point of view, may be a new option could be added under "Null analysis" category, something like "Null argument passed to overloaded method"