[Issue 11847] Importing "package.d" module causes qualified name lookup to fail for sub modules

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=11847

--- Comment #7 from Jonathan M Davis <jmdavisProg at gmx.com> ---
Also, keep in mind that the whole reason to add package.d to the language in
the first place was to be able to break up a module into a package, in which
case, it's intended as a migration path and not necessarily as something
permanent, so making it so that importing a package conflicts with importing
its individual modules is very likely to cause problems - especially if new
modules with code that wasn't in the original module that was split are added
after it's been split (since they likely wouldn't be publicly imported in the
package.d file, because that's unnecessary for migration).

--