Bug 2919 – Using .di files, does not always get all public imports

ATM i have no small test case for this. In DWT2 there is: java.lang.String: alias char[] String; java.lang.all: public import java.lang.String; org.eclipse.jface.viewers.ICellValidator: import java.lang.all; interface ICellValidator{ public String isValid(Object o); // [1] } This compiles fine to a lib and the .di files are build also without problems. Also application can compile with the generated headers. Now when building an application only the generated .di and the build libs shall be used. But in some scenarios the compiler complains at [1] (in the generated .di) that 'String' is not known. This happens also with other files that have interface definitions. To work around the problem, i can add the java.lang.String import to the module with the interface. But that is obviously not a good solution, because it still means that DMD is broken here. I tried to play around with a few files, but was not able to trigger the bug. So i file this bug report, so i can refer to it in my code where i put in those work around imports.

I'm going to close this as there is no code snippet to reproduce and the bug might have been fixed in the meantime. If you discover a reproducing example, please file it as new issue.