Re: Nim - Unique Module Names

[Araq]

The restriction exists so that `nimblepackage.module.symbol` is a non-ambiguous 
path to `symbol`. Backends benefit from this restriction but it's about 
enforcing a coding style that makes it easier to follow, or talk about the code 
("look at module M, argh no, not that one, that other thing in /I/lng/fr/vwls").