named import are always public

[Gary Willoughby]

On Tuesday, 10 September 2013 at 08:22:18 UTC, Namespace wrote:
> I have already found an old bug report for this, but I do not 
> understand why it has still not been solved. Can someone 
> explain that to me?
>
> Example:
>
> a.d:
> ----
> module a;
>
> private import std.stdio : writeln;
> ----
>
> b.d:
> ----
> import a;
>
> void main() {
> 	writeln("This is wrong.");
> }
> ----
>
> WTF? writeln should be private.
> I don't like this. :P

This is a WTF, where's the old report?