Bug 516946 - Add documentation for unlikely argument type compile
problems
Change-Id: Ic3d0bf35b25376deb65a676bfb71c28ee7b75378
diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/compiler/ref-preferences-errors-warnings.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/compiler/ref-preferences-errors-warnings.htm
index 8d2a4be..d34c329 100644
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/compiler/ref-preferences-errors-warnings.htm
+++ b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/compiler/ref-preferences-errors-warnings.htm
@@ -218,6 +218,45 @@
</tr>
<tr>
<td valign="top">
+ <p>Unlikely argument type for collection methods using 'Object'</p>
+ </td>
+ <td valign="top">
+ <p>When enabled, the compiler will issue an error or warning when certain well-known Collection methods
+ that take an 'Object', like e.g. 'Map#get(Object)', are used with an argument type,
+ that seems to be not related to the corresponding type argument of the Collection.</p>
+ </td>
+ <td valign="top">
+ <p>Warning</p>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top" style="padding-left: 2em;">
+ <p>Perform strict analysis against the expected type</p>
+ </td>
+ <td valign="top">
+ <p>By default, this analysis will apply some heuristics to determine whether or not two
+ types may or may not be related, which can be changed via this option. When enabled, the heuristics will be replaced with strict compatibility checks,
+ i.e., each argument that is not strictly compatible with the expected type will trigger an error or warning.</p>
+ </td>
+ <td valign="top">
+ <p>Off</p>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top">
+ <p>Unlikely argument type for method equals()</p>
+ </td>
+ <td valign="top">
+ <p>When enabled, the compiler will issue an error or warning when 'java.lang.Object#equals(Object)' is used with an argument type,
+ that seems to be not related to the receiver's type, or correspondingly when the arguments of 'java.util.Objects#equals(Object, Object)'
+ have types that seem to be not related to each other.</p>
+ </td>
+ <td valign="top">
+ <p>Info</p>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top">
<p>Empty statement</p>
</td>
<td valign="top">
