Open dom96 opened 8 years ago
So with #635, nimble files are just executed with nim e
. Assuming that PR goes through, is there something extra needed within nimble?
Nim only allows imports at the top level so seems like this should be tracked there.
I think I had a fancy mechanism in mind that would allow importing modules that are perhaps offered by other packages, this would mean that the imports would need to be in the tasks and that the tasks would only be executable when those packages are installed. It's possible this isn't really all that useful.
I propose closing this.
I'll demote this, but I'd like to keep it as a potential feature/idea.
This may need to be done at runtime, because placing an import statement at the top of a Nimble file will cause the module to be imported each time the Nimble file is evaluated.