|
113 | 113 | * annotation in this location could only be either contradictory or redundant. |
114 | 114 | * <li>On a <b>local variable</b> declaration (root type only). While the cases listed above |
115 | 115 | * benefit from <i>declarative</i> nullness, the nullness of a local variable is more properly |
116 | | - * determined through flow analysis (<a href="https://bit.ly/3ppb8ZC">Why?</a>). This rule |
| 116 | + * determined through flow analysis (<a |
| 117 | + * href="https://jspecify.dev/docs/nullness-design-faq/#local-variables">Why?</a>). This rule |
117 | 118 | * applies only to the <i>root type</i> of the variable; type components, such as type |
118 | 119 | * arguments, follow the usual rules. |
119 | 120 | * <li>In a <b>cast expression</b> (root type only). To inform an analyzer that an expression it |
120 | 121 | * sees as nullable is truly non-null, use an assertion or a method like {@link |
121 | | - * java.util.Objects#requireNonNull}. (<a href="https://bit.ly/3ppb8ZC">Why?</a>) Type |
122 | | - * components, such as type arguments, follow the usual rules. |
| 122 | + * java.util.Objects#requireNonNull}. (<a |
| 123 | + * href="https://jspecify.dev/docs/nullness-design-faq/#casts">Why?</a>) Type components, such |
| 124 | + * as type arguments, follow the usual rules. |
123 | 125 | * <li>On any part of the argument to <b>{@code instanceof}</b>. The root type is intrinsically |
124 | 126 | * non-null, as discussed above, and nothing else about nullness is checked at runtime. |
125 | 127 | * <li>On any part of a <b>receiver parameter</b> type (<a |
|
0 commit comments