[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

Jonathan M Davis <jmdavisProg at gmx.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jmdavisProg at gmx.com

--- Comment #6 from Jonathan M Davis <jmdavisProg at gmx.com> ---
I also agree with Sönke. There should be no difference between publicly
imported modules in package.d and publicly imported modules in any other
module. All package.d should be doing is making it so that when you import the
package, you import package.d instead. It shouldn't have any other effects.

import test;
import test.mod;

should work just as well as

import std.array;
import std.range;

does. std.array.uninitializedArray doesn't suddenly stop working just because
you also imported std.range, which publicly imports std.array.

--