Description Stephan Herrmann 2018-10-30 14:58:50 EDT

(In reply to Greg Woolsey from bug 484467 comment #3)
> [...]
> Note that the same error happens when the Test class is moved to its own
> source file in the same package.  In that case, it appears the Eclipse
> compiler is confusing the enum with the same name vs. the class with that
> name.  However, the ::new reference must be to a type, not an Enum instance,
> which is how javac knows which one to reference. 
> 
> A workaround is to reference the class in the ::new constructor argument
> with its fully qualified class name.  Then the Eclipse compiler understands
> which "Test" is being referenced.  However, javac shows this is not
> required, and that the source ordering used by Eclipse is not flexible
> enough to handle this case and the original case for this bug.
> 
> public enum EclipseCompileBug {
> 	/*
> 	 * Next line fails with these errors in Eclipse, works with javac:
> 	 * <li>Test cannot be resolved to a type
> 	 * <li>Cannot reference a field before it is defined
> 	 */
> 	Test(Test::new);
> 
> 	@FunctionalInterface
>     public interface IConstructor<T extends Object> {
>         T apply();
>     }
> 
>     private final IConstructor<?> constructor;
> 	private EclipseCompileBug (IConstructor<?> newObj) {
> 		constructor = newObj;
> 	}
> 	
> 	public static class Test {
> 		
> 	}
> }