-
Notifications
You must be signed in to change notification settings - Fork 35
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
contribution guidelines for adding multi-file modules/libraries? #26
Comments
One that came to mind is tomlin. |
Or is spork better kept simple and for single-file modules? |
Currently, I think spork is best served by smaller, janet only modules. One reason for this is adding C modules means it may be harder to install in some platforms, but I'm not making a hard line here. |
Thank you very much for the answer. I will link the answer to the spork discussion. |
I guess we can close this, @uvtc. |
Yup. Thanks. |
It looks to me like spork currently contains only single-file modules. However, some modules that may be a good fit for inclusion into spork may contain multiple files, their own tests, docs, etc. It is not clear how one would create a PR for inclusion of modules/libraries of this type. Would it make sense for there to be a contributions doc for this repository, specifically including guidelines for how to weave in these kinds of "larger" libraries?
The text was updated successfully, but these errors were encountered: