Bug 561131 - Content assist chooses wrong method for multiple inheritance
Summary: Content assist chooses wrong method for multiple inheritance
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.14   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-15 17:48 EDT by Ivan CLA
Modified: 2024-02-25 15:44 EST (History)
0 users

See Also:

Attachments
default vs virtual (243.37 KB, image/png)
2020-03-15 17:50 EDT, Ivan CLA 		no flags Details
default vs virtual with covariant (197.71 KB, image/png)
2020-03-15 17:51 EDT, Ivan CLA 		no flags Details
View All 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 Ivan CLA 2020-03-15 17:48:28 EDT 
When we have "multiple inheritance" for method with the same signature (with or without covariant return type), content assist (CA) can show wrong method description. Such cases are known:
1) abstract interface method + exact class method. CA chooses interface, while class should be chosen.
2) default interface method + exact class method. CA chooses interface, while class should be chosen.

Mark occurrences works fine though.

Images will be attached. Red lines show correspondence of incorrect parts.
Comment 1 Ivan CLA 2020-03-15 17:50:33 EDT 
Created attachment 282114 [details]
default vs virtual
Comment 2 Ivan CLA 2020-03-15 17:51:06 EDT 
Created attachment 282115 [details]
default vs virtual with covariant
Comment 3 Eclipse Genie CLA 2022-03-06 07:25:57 EST 
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 2024-02-25 15:44:45 EST 
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.