Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to import NimScript modules in tasks #181

Open
dom96 opened this issue Dec 30, 2015 · 4 comments
Open

Ability to import NimScript modules in tasks #181

dom96 opened this issue Dec 30, 2015 · 4 comments

Comments

@dom96
Copy link
Collaborator

dom96 commented Dec 30, 2015

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.

@genotrance
Copy link
Contributor

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.

@dom96
Copy link
Collaborator Author

dom96 commented Apr 18, 2019

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.

@genotrance
Copy link
Contributor

I propose closing this.

@dom96
Copy link
Collaborator Author

dom96 commented Sep 5, 2019

I'll demote this, but I'd like to keep it as a potential feature/idea.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants