Namespace for a module defined by its import path

[Adam D. Ruppe via Digitalmars-d]

On Monday, 24 October 2016 at 23:26:09 UTC, bitwise wrote:
> Not sure if I understand you correctly, but you're allowed to 
> omit the module declaration, if that helps:

It doesn't help, I strongly recommend you ALWAYS use the explicit 
module definition. If you leave it out, you'll regret it sooner 
or later.

The automatic module name never has a package component, it is 
just one word, and is thus highly likely to cause name conflicts 
later.