Bug 500151 - ITypeBinding#getBinaryName() returns incorrect value for TypeVariable's defined by a generic method
Summary: ITypeBinding#getBinaryName() returns incorrect value for TypeVariable's defin...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.5.2   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Jay Arthanareeswaran CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-23 13:00 EDT by Goktug Gokdogan CLA
Modified: 2022-07-24 13:25 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 Goktug Gokdogan CLA 2016-08-23 13:00:04 EDT 
Per http://docs.oracle.com/javase/specs/jls/se8/html/jls-13.html#jls-13.1:

"The binary name of a type variable declared by a generic method (§8.4.4) is the binary name of the type declaring the method, followed by $, followed by the descriptor of the method (JVMS §4.3.3), followed by $, followed by the simple name of the type variable.:


JLS defines the name of the method as part of the binary name; since it is missing; the API doesn't correctly follow its contract and the generated names are not unique.

Also see https://bugs.eclipse.org/bugs/show_bug.cgi?id=107001
Comment 1 Jay Arthanareeswaran CLA 2016-08-24 02:40:44 EDT 
Keeping tentatively in 4.7.
Comment 2 Manoj N Palat CLA 2018-05-21 06:13:52 EDT 
Bulk move out of 4.8
Comment 3 Eclipse Genie CLA 2020-05-28 02:15:17 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 Eclipse Genie CLA 2022-07-24 13:25:47 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.