Bug 485661 - [1.8][null] bogus conflict reported between @NonNull type variable and its @Nullable upper bound
Summary: [1.8][null] bogus conflict reported between @NonNull type variable and its @N...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.5.1   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2016-01-12 09:27 EST by Stephan Herrmann CLA
Modified: 2022-06-23 15:46 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stephan Herrmann CLA 2016-01-12 09:27:53 EST 
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.
Comment 1 Manoj N Palat CLA 2018-05-17 03:25:44 EDT 
bulk move out of 4.8
Comment 2 Manoj N Palat CLA 2018-08-17 00:11:10 EDT 
Bulk move out of 4.9
Comment 3 Eclipse Genie CLA 2022-06-23 15:46:38 EDT 
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.