Thank you for the explanation.
Yes, I'm really with you on the idea of enforcing the coding style.
I'm not fully sure yet, but looks like I'm having a case where it would be
better (for the sake of simpler/clearer software design) to distinguish symbols
basing on the filesystem path.
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 /
Why there is a restriction "module names need to be unique per Nimble package" ?
Is this restriction of the Nim language or just a temporary inability of the
C-backed ?
