Bug 172925 - [5.0][content assist] Content Assist for unbound wildcard shows type as "null"
Summary: [5.0][content assist] Content Assist for unbound wildcard shows type as "null"
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.2.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 355361 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-02-05 16:35 EST by Alan Malloy CLA
Modified: 2022-08-29 04:13 EDT (History)
3 users (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 Alan Malloy CLA 2007-02-05 16:35:52 EST 
Build ID: M20060921-0945

Steps To Reproduce:
Given that java.util.ArrayList is imported, enter the following in a method and use Ctrl-Space to activate Content Assist:

new ArrayList<?>([cursor]

Two correct proposals are given, but one incorrect one is supplied as well: ArrayList(null c). This proposal comes from the constructor ArrayList<E>(Collection<? extends E>), but it seems that Eclipse is confused by the construct when E is unbound: ArrayList<?>(Collection<? extends ?>).

More information:
The correct behavior is for Content Assist to suggest ArrayList(Collection<?>).
Comment 1 Dani Megert CLA 2011-08-22 08:45:58 EDT 
*** Bug 355361 has been marked as a duplicate of this bug. ***
Comment 2 Eclipse Genie CLA 2020-07-17 18:33:15 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.
Comment 3 Eclipse Genie CLA 2022-08-28 18:47:27 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.
Comment 4 Mauro Molinari CLA 2022-08-29 04:13:52 EDT 
Still applies to 2021-12.