Summary: | [null] @Nullable declaration ignored rather than overriding flow analysis | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Ed Willink <ed> |
Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
Status: | NEW --- | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 4.13 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows 10 | ||
Whiteboard: |
Description
Ed Willink
2019-06-23 04:12:15 EDT
Use org.eclipse.jdt.annotation.Checks.isNull(Object) This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. The original problem has not been addressed by comment #1. Rather a suggestion to code differently is given. Alternative code will indeed often avoid a bug, but the bug still needs to be addressed. The suggested alternative has stronger org.eclipse.jdt.annotation dependency, requiring a mandatory rather than optional bundle. |