Bug 514217 - [1.8][inference] check necessity of BoundSet.getEquivalentOuterVariable()
Summary: [1.8][inference] check necessity of BoundSet.getEquivalentOuterVariable()
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.7   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-26 15:21 EDT by Stephan Herrmann CLA
Modified: 2022-11-05 15:13 EDT (History)
0 users

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 2017-03-26 15:21:58 EDT 
Inspecting said method (which was introduced on behalf of bug 452788), I have the feeling this may no longer be necessary after work in the area of Bug 506016.

Hint in favor of removing: part of this method has always been wrong, as detected in bug 513790.
Comment 1 Manoj N Palat CLA 2018-05-16 01:30:07 EDT 
Bulk move out of 4.8
Comment 2 Eclipse Genie CLA 2020-09-16 11:31:08 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-11-05 08:14:48 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 Stephan Herrmann CLA 2022-11-05 15:13:35 EDT 
As of today, org.eclipse.jdt.core.tests.compiler.regression.TestAll passes even with BoundSet.getEquivalentOuterVariable() constantly returning null.

Right now I'm not sure if that's sufficient proof of obsolence.