I forgot, but i was also wondering why we have to import our own project's 
files at all to begin with. Why not have the concept of `local imports` and 
`remote imports`, where for `local imports`, the compiler checks my `.nim` and 
`.nimf` files and imports anything i'm using, and where `remote imports` 
(nimble-installed modules, nim std, anything not in my local project dir) would 
still be treated as they are now.

If necessary, dir(s) could be defined for `local imports` similar to my 
original question. I suppose you could also continue to manually import local 
modules if you needed to for a name conflict you didn't want to rename for some 
reason, or if one just prefers the current import method.

Am i missing something basic, or lang devs just never thought it was important 
enough to bother with?

Reply via email to