About Go, D module naming

[Walter Bright]

On 12/21/2012 8:38 PM, Jonathan M Davis wrote:
>> The reason it is that way is to avoid having it behave gratuitously
>> differently than how visibility works within classes and structs.
>
> ??? I don't see anything here that would become different between user-defined
> types and modules.
>
> All we're really asking for here is that inaccessible symbols not be put in
> overload sets.

But they are in structs in classes (following the way C++ does it).