Bug 395655 - Code Assist does not work with anonymous class in enum constructor
Summary: Code Assist does not work with anonymous class in enum constructor
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.2.1   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
: 420512 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-12-03 22:07 EST by Matt Ring CLA
Modified: 2022-08-22 15:57 EDT (History)
4 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 Matt Ring CLA 2012-12-03 22:07:53 EST 
package pkg1;


public enum Foo {
	
	Bar(new Runnable() {
		public void run() {
			// code assist won't work here
		}
	}),
	Baz(new Runnable() {
		public void run() {
			// code assist won't work here, either
		}
	});
	
	private final Runnable runnable;
	private Foo(final Runnable runnable) {
		this.runnable = runnable;
	}
	
	public void doSomething() {
		this.runnable.run();
	}

}
Comment 1 Dani Megert CLA 2012-12-04 02:24:07 EST 
Looks similar to bug 395604.
Comment 2 Dani Megert CLA 2013-10-28 11:42:03 EDT 
*** Bug 420512 has been marked as a duplicate of this bug. ***
Comment 3 Eclipse Genie CLA 2020-08-11 11:41:09 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-08-22 15:57:15 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.