public import and bugs it causes

[Walter Bright]

bearophile wrote:
> Nick Sabalausky:
> 
>> 1. The problem he had had nothing to do with public imports. Any of the 
>> modules he was importing could just as easily had a global var named "name"
>> 
> 
> Yes, that's caused by another hole in the design of D module system, that I
> hope to see fixed someday. It's almost three years from the first time I have
> reported it, probably in my second post on D newsgroups.

I don't agree that it's a hole or a bug. The designer of an imported module has 
complete control over what names will be visible to the importer and which 
aren't. This is as it should be.