Bugzilla – Full Text Bug Listing
| Summary: | [1.8][null] bogus conflict reported between @NonNull type variable and its @Nullable upper bound | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Stephan Herrmann <stephan.herrmann> |
| Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | manoj.palat |
| Version: | 4.5.1 | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | stalebug | ||
bulk move out of 4.8 Bulk move out of 4.9 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. |
NTAT.testBinary06() expects this error: public class X2<@NonNull W extends @Nullable Object> {} ^^^^^^^^^ This nullness annotation conflicts with a '@NonNull' annotation which is effective on the same type parameter This doesn't make sense, since "extends @Nullable" imposes no restriction. The given snippet is meaningless, but not erroneous.