Nested public imports - bug or feature?

[Dicebot via Digitalmars-d]

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