Nested public imports - bug or feature?

[Dejan Lekic via Digitalmars-d]

On Thursday, 13 August 2015 at 16:22:04 UTC, Dicebot wrote:
> On Thursday, 13 August 2015 at 16:19:29 UTC, Jonathan M Davis 
> wrote:
>> You can get that behavior with static imports in D, but having 
>> to use the whole import path while referencing symbols gets 
>> ugly fast.
>
> Check example again, you are only required to use the plain 
> module name, not fully qualified one. With D syntax:
>
> import std.stdio;
>
> writeln(); // not good
> stdio.writeln(); // good
> std.stdio.writeln(); // also good, but not required

Thank God, D does it the "not good" way. But I guess that is 
subjective thing. Some people like it one way, others like it the 
other way.

I humbly belive D's way is good. Compiler should issue a warning 
when conflicts arrive. This is not Python for Haven's sake!