About Go, D module naming

[Walter Bright]

On 12/21/2012 12:44 AM, Timon Gehr wrote:
> ... modulo the private symbol clash issue. For all I know it is deliberate,
> which is embarrassing. Other than obviously breaking modularity, it severely
> restricts the usefulness of symbol disambiguation (which it makes necessary when
> it should not be), because the disambiguating alias may introduce more conflicts
> even if it is private, all over the code base.

The reason it is that way is to avoid having it behave gratuitously differently 
than how visibility works within classes and structs.