Mirror of forum.nim-lang.org

2937 :: Nim - Unique Module Names

[2017-05-03T19:53:29+02:00]

ivanitto (orginal) [2017-05-03T19:53:29+02:00] view original

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 ?

Araq (orginal) [2017-05-03T22:32:38+02:00] view original

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").

ivanitto (orginal) [2017-05-05T21:27:49+02:00] view original

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.