-
Notifications
You must be signed in to change notification settings - Fork 16
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
Releases #1
Comments
Will this also imply that all the modules are downloaded and updated instead of piece-meal? |
There are no git submodules, there is only code that works well with Nim 1.0 and upcoming releases. |
I was just wondering, if fusion is ultimately the embodiment of the nim distribution idea, how/when each component module is updated. Maybe it would help to do a series of questions: (1) Will fusion be an independently-installable nim module? (actually I think the readme answers this in the affirmative) |
(1) Yes. Fusion is not the "Nim distribution" idea, it's trimmed down to what we think is maintainable for our current team. Of course, the team can grow or shrink, but we manage it just like Nim's stdlib. |
Aha, thanks for clarifying |
Do you have an idea about how fusion releases will work, if it's composed of many submodules that are updated independently? I'm guessing the submodules are independently versioned and that "fusion" is a nimble-installable module.
The text was updated successfully, but these errors were encountered: