Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 479002

Summary:	Follow up bug for 477891 - clean up and improvements in MethodVerifier
Product:	[Eclipse Project] JDT	Reporter:	Sasikanth Bharadwaj <sasikanth.bharadwaj>
Component:	Core	Assignee:	Sasikanth Bharadwaj <sasikanth.bharadwaj>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	stephan.herrmann
Version:	4.6
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:	stalebug

Description Sasikanth Bharadwaj

2015-10-05 03:52:39 EDT

There are still some improvements in MethodVerifier which were brought to light by the fix for bug 477891. This bug is intended to follow up on these and see what can be done.
Pasting the relevant comment here for convenience

(4) At this point I started suspecting that we could remove the doesMethodOverride() checks inside checkInheritedDefaultMethods(), producing (just) 2 failures in InferenceMethodsTest: testBridge01() and test426318().

(5) On analyzing the failure in testBridge01() I saw that findReplaceMethod() introduced a near-duplicate: matchingInherited would contain a method plus its m.asRawMethod() variant. A conflict was reported against these near-duplicates. Avoiding the asRawMethod() conversion on this particular call chain (controlled by a new flag convertToRaw) and avoiding the duplicate entry into matchingInherited could fix this failure.

(6) I did not analyze the failure in test426318().

Items (4) - (6) are not directly coupled to the issue at hand, these are just attempts to better understand and then clean-up our code.

Comment 1 Eclipse Genie

2019-08-02 02:48:26 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.