Bug 491998 - [impl] Suspecious looking code in LookupEnvironment.createWildcard(ReferenceBinding, int, TypeBinding, TypeBinding[], int)
Summary: [impl] Suspecious looking code in LookupEnvironment.createWildcard(ReferenceB...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.6   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-04-19 09:05 EDT by Stephan Herrmann CLA
Modified: 2022-06-25 13:16 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-04-19 09:05:12 EDT 
(In reply to Till Brychcy from bug 485988 comment #6)
> While examining this, I've found some suspicious looking code: it looks like
> in LookupEnvironment.createWildcard(ReferenceBinding, int, TypeBinding,
> TypeBinding[], int), the type annotations from the GenericType are passed to
> typeSystem.getWildcard as annotations for the Wildcard (but I think this is
> never actually executed for an annotated GenericType). Or have I
> misunderstood something?

This code was introduced via Bug 455180, and indeed there's a significant difference between createParameterizedType(), createRawType() (both look good) versus createWildcard(), where genericType plays a different role.
Comment 1 Manoj N Palat CLA 2018-05-17 03:23:08 EDT 
bulk move out of 4.8
Comment 2 Manoj N Palat CLA 2018-08-16 00:09:16 EDT 
Bulk move out of 4.9
Comment 3 Eclipse Genie CLA 2022-06-25 13:16:52 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.