https://issues.dlang.org/show_bug.cgi?id=15086
--- Comment #21 from Walter Bright <bugzi...@digitalmars.com> --- (In reply to ag0aep6g from comment #19) Thank you for providing a simple and clear test case to illustrate the issue. It is indeed a problem that the order of imports is mattering, as this breaks a fundamental tenet of D's import system. I have not thought about this thoroughly, but I suspect the core of a fix can be along the lines of detecting that an explicit import of bar.d is done using two different names in the same module. This is a lot more focused in effect than the PR. --